The latest version (2013.06.14) of the "LIVE555 Streaming Media" code changes the signature of the constructor of the "RTSPClient" class, and of its subclass "ProxyRTSPClient". If you have subclassed either of these classes in your code, then you will need to make a small change to your code accordingly.
The change is to add a 'socket number to server' parameter (as the final parameter to the constructor). This socket number (if >=0) is the socket of an existing TCP connection to the server. This allows you to create a RTSP client object from an existing TCP connection. (If you do this, the supplied "rtsp://" URL must point to the server that's at the endpoint of the TCP connection.) If the 'socket number to server' parameter is <0 (e.g., -1), then the old behavior remains: A new TCP connection will be created for the class, by resolving the "rtsp://" URL. (The "RTSPClient::createNew()" function also takes a 'socket number to server' parameter, but this has a default value of -1, so existing code that creates "RTSPClient"s using only the "createNew()" function will not need to change.) Ross Finlayson Live Networks, Inc. http://www.live555.com/ ps. I've also defined and implemented a custom "REGISTER" command that a server can use to notify a client (or a proxy) about the existence of one of its streams. The client (or proxy) can then use the same TCP connection to access the stream. This can be useful if the client (or proxy) is publicly accessible, but the server is behind a firewall or NAT. I'm not quite ready to release this feature yet, but should be able to soon. Stay tuned...
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
