In looking at openConnectionFromURL() I think I see a potential
problem with fBaseURL.
Basically the first thing this method does is free fBaseURL and then
strDup the new URL.
Next this method parses the url and then checks to see if it a input
socket is open and if not opens one using the URL.
If parsing fails or an input socket is already open the function
aborts and doesn't clean up fBaseURL.
The problem I see is if a socket where opened to a URL and then
never closed before calling openConnectionFromURL with another URL
fBaseURL could be set to a URL that doesn't match the URL the socket
is connected to.
This seems like a potential for a bug or at the very least much confusion.
A single "RTSPClient" instance (at least, in its current
implementation) was never intended to support more than one RTSP URL
- either concurrently, or successively. You should use a different
"RTSPClient" object for each RTSP URL that you want to handle.
--
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
