Re: [Live-devel] Tricky bug in RTSP-on-HTTP server implementation?

2010-10-22 Thread Ross Finlayson
OK, I have now installed a new version (2010.10.23) of the "LIVE555 Streaming Media" code that should overcome this problem. -- Ross Finlayson Live Networks, Inc. http://www.live555.com/ ___ live-devel mailing list live-devel@lists.live555.com http://l

Re: [Live-devel] Tricky bug in RTSP-on-HTTP server implementation?

2010-10-22 Thread Ross Finlayson
Can you confirm me it's a bug? Yes, it appears to be a bug. I'm curious, though: Does it still occur (sometimes) even with an up-to-date version of "openRTSP"? The version that you're using - 2010.04.09 - is very old; our RTSP client implementation has changed significantly since then. --

[Live-devel] Tricky bug in RTSP-on-HTTP server implementation?

2010-10-22 Thread Cristiano Belloni
Dear Ross, I noted a very strange behaviour with you latest liveMedia implementation. On my workstation (Linux OS), it works like a charm. On other systems (with Linux OS as well), it seems not to respond to the OPTIONS post, time-outing every client (except openRTSP, that after ~ 30 seconds tr

Re: [Live-devel] RTSP-over-HTTP question

2010-10-22 Thread Ross Finlayson
No, the problem is that the server is completely ignoring the resending of the HTTP "GET" command Yes, the server ignores this request but it does it because it is closing a connection. The server can't be closing the connection, otherwise it would never be able to stream back data to the cl

Re: [Live-devel] RTSP-over-HTTP question

2010-10-22 Thread Kamil Dobkowski
No, the problem is that the server is completely ignoring the resending of the HTTP "GET" command Yes, the server ignores this request but it does it because it is closing a connection. I tried `live.2010.01.22` and it is working fine with this server - it doesn't try to send a second request

Re: [Live-devel] RTSP-over-HTTP question

2010-10-22 Thread Ross Finlayson
and that's all ... I see no other requests sent to the server. I think the problem is beacause this server does not immediately close its connection after http reply, so client is able to send a repeated request during the same connection but it is ignored by the server. No, the problem is th