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 to the message with a 200?
In my logs it appears the Session header is sent in the OPTIONS command but assume a OPTIONS is not session dependent it will ignore any session header. So I guess my point is how the session header would be honored in a OPTIONS vs GET_PARAMETER. Seems the GET_PARAMETER is a better solution. Thanks, Craig On 03/04/2014 04:32 PM, Ross Finlayson wrote: 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 the session has failed, It will then reset its state with the back-end server. It will then attempt to send another "DESCRIBE" command (and then "SETUP", "PLAY", etc. for any subsequent front-end client connection(s). Note that this is true *regardless* of whether the 'liveness' command is "OPTIONS" (by default), or "GET_PARAMETER" (if you've "#define"d SEND_GET_PARAMETER_IF_SUPPORTED). So I don't understand the "OPTIONS vs GET_PARAMETER" in your "Subject:" line. Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
