Peter, Thanks for the report. Yes, you're correct that the current code is buggy - it should not be doing more than one potentially blocking socket read inside the read handler (because the second and subsequent reads might, indeed, block). It seems a bit strange that a client would behave in such a way as to make this a problem, but certainly the server should not be relying upon correct client behavior.
In the next released version of the code, I'll see if I can find a way to make this code more bullet-proof - most likely using timeouts on the socket reads, as you suggested. -- Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
