>On Sat, Aug 04, 2007 at 02:58:37AM -0700, Ross Finlayson wrote:
>> However, I don't think a client could really do much that is useful
>> should it see this parameter. Client 'liveness' is indicated by RTCP
>> "RR" packets, which the client sends frequently already.
>>
>> In other words, I do
Hi again,
On Sat, Aug 04, 2007 at 02:58:37AM -0700, Ross Finlayson wrote:
> However, I don't think a client could really do much that is useful
> should it see this parameter. Client 'liveness' is indicated by RTCP
> "RR" packets, which the client sends frequently already.
>
> In other words,
The timeout interval (i.e., how long the server waits before timing
out a session due to client inactivity) is something that is
determined by the *server*, not by the client. The default timeout
is 45 seconds; however, you can change this (in the
"reclamationTestSeconds" parameter to "RTSPSer
Hello everyone,
I spotted a small problem with timeouts using live555 and vlc: when
an RTSP server does not give an explicit timeout for the session,
live555 RTSP client does not use the implicit 60 second timeout
specified in the RFC. Would things break seriously if you changed
the constructor of
I couldn't follow all of this (especially the bizarre final
question), but one thing you should note - that may be relevant - is
that, in our current RTSP server implementation, each "PLAY", "PAUSE"
and/or "TEARDOWN" command must use the same TCP connection as the
original "SETUP" command. (Th
