<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">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.<br>
<br>
Thanks,<br>
Craig<br>
<br>
On 03/04/2014 05:47 PM, Jeff Shanab wrote:<br>
</div>
<blockquote
cite="mid:CAM09syq5AkESaGt9uy4OBjfvd86ivt=Api+OkUDmYfxHXkzQ7w@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>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,
I reference counted my frames and when that reference count
hit zero it returned the frame object to the pool. Not sure
if that answers your question.<br>
</div>
Part of this is basic sockets. I was using TCP. It KNOWs when a
connection is broken. I couldn't wait for it so I added the
watchdog.<br>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Tue, Mar 4, 2014 at 6:59 PM, Craig
Matsuura <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:cmatsuura@vivint.com" target="_blank">cmatsuura@vivint.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>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?<br>
<br>
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.<br>
<br>
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.<br>
<br>
Thanks,<br>
Craig<br>
<br>
<br>
On 03/04/2014 04:32 PM, Ross Finlayson wrote:<br>
</div>
<blockquote type="cite"> I'm not sure I understand your
question.
<div><br>
</div>
<div>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).</div>
<div><br>
</div>
<div>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.</div>
<br>
<br>
<div> <span><span
style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;white-space:normal;font-family:Helvetica;word-spacing:0px">Ross
Finlayson<br>
Live Networks, Inc.<br>
<a moz-do-not-send="true"
href="http://www.live555.com/" target="_blank">http://www.live555.com/</a></span></span>
</div>
<br>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
live-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a><br>
<a moz-do-not-send="true"
href="http://lists.live555.com/mailman/listinfo/live-devel"
target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>