[Live-devel] RTSPClient blocking/non-blocking bug?
finlayson at live555.com
Fri Jan 15 06:33:35 PST 2010
>...I see that if timeout > 0, then fInputSocketNum is set to a
>non-blocking socket (i.e. makeSocketNonBlocking). Shouldn't this
>get set back to a blocking socket once this connect attempt is
>(it may be that this happens somewhere else, but my quick checks
>through the code didn't reveal any such code)
>If this is an issue, I have code I can submit that will set the
>socket back to blocking.
Yes, please submit a patch. Thanks.
Live Networks, Inc.
More information about the live-devel