I’m not sure what exactly you’re asking here. When receiving a RTP/RTCP-over-TCP stream (i.e., on the RTSP TCP connection), we certainly do handle socket read errors, if they occur. But the actual socket itself (for the RTSP TCP connection) is not closed until the “RTSPClient” decides that it should be closed. Once streaming has started (i.e., when we’re no longer handling RTSP commands), then this doesn’t happen until the “RTSPClient” object itself is closed.
But I’m not going to get into a ‘rat hole’ discussing arcane details of the internals of the code (that you should not need to concern yourself with). If (and only if) you discover an actual bug (not just a suspected bug) in the code, then please let us know. (As always, this needs to be with the unmodified, latest version of the code.) 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
