Re: [Live-devel] OPTIONS vs GET_PARAMETER for keep alive with proxy server

2014-03-09 Thread Craig Matsuura
Thanks for the insight Jeff. After further digging I found the issue we were having. I have moved back to OPTIONS as a keepalive. I posted a patch to the mailing list but have not seen it approved. Thanks, Craig On 03/04/2014 05:47 PM, Jeff Shanab wrote: In my Archiver, Restreamer, and Player

Re: [Live-devel] OPTIONS vs GET_PARAMETER for keep alive with proxy server

2014-03-05 Thread Jeff Shanab
In my Archiver, Restreamer, and Player I have a watchdog that is kicked when frames come in. If I fail to get frames the watchdog expires; or if ever there is a socket error. It is a do-over. I start again with the DESCRIBE. I did my own server and there was never more than 1 stream from the camera

Re: [Live-devel] OPTIONS vs GET_PARAMETER for keep alive with proxy server

2014-03-04 Thread Craig Matsuura
It appears the GET_PARAMETER will accept the Session header as a OPTIONS does not care. So if for some reason the camera server closes the session what is the indicator to the client? If the GET_PARAMETER is sent with a Session I assume the camera server should respond with a 454 and not reply

Re: [Live-devel] OPTIONS vs GET_PARAMETER for keep alive with proxy server

2014-03-04 Thread Ross Finlayson
I'm not sure I understand your question. If the 'liveness' command from the proxy server (*either* "OPTIONS" or "GET_PARAMETER") fails - either because the TCP connection fails, or because the back-end server responded with a response code other than 200 - then the proxy server will assume that