#35 Automatic Port Determination not working


When I run the samples and start the Control-point client together with the TV sample, which also contains a control-point, one of the two applications does not initialize correctly, it cannot bind to port 8009, as this is already in use by the other one.

This is due to the fact that initialization is done in the constructor of the HTTPUSocket (an dereived classes). A failure in the constructor cannot be signaled to the caller, so that loop, where different ports are tried, is not executed as a failure is not detected at the moment.

A fix might to move the init code into a static factory method and return null in case of failure, so that the loop can start another try.


Log in to post a comment.