> If you attempt to receive a stream from an invalid source, (i.e.
> rtsp://non-existing_IP:554/main)
> then the testRTSPClient application will crash.
>
> It seems that calling Medium::close() is the culprit. Medium::close() works
> fine when connected to a valid stream, but will cause heap co
> Sir i don't want to use the live media library rather want to receive the
> data through sockets.
Well, if you don't want to use our software, then your question is off-topic
for this mailing list. You'll need to ask somewhere else. Sorry.
Ross Finlayson
Live Networks, Inc.
http://www.liv
Hi;
If you attempt to receive a stream from an invalid source, (i.e.
rtsp://non-existing_IP:554/main)
then the testRTSPClient application will crash.
It seems that calling Medium::close() is the culprit. Medium::close() works
fine when connected to a valid stream, but will cause heap corruption
Sir i don't want to use the live media library rather want to receive the
data through sockets.
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
Hi Ross,
Actually the "extension" is implemented in terms of RFC 2326 by using
"Require" header (12.32 Require).
So the question is how to get these "Require" headers from OPTIONS
request and respond with 200 OK or 551 Option not supported.
The second part of question is how to make a track w
