<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Live-devel] Problems with RTSPClient, CSeq
variable</title></head><body>
<blockquote type="cite" cite>This is what I'm doing and haven't had a
problem yet with our test servers. What I'm more interested in is from
the original post:<br>
<blockquote>Does LiveMedia library conform to RTSP standard in this
matter or maybe it is a bug in Sanyo devices ?</blockquote>
<blockquote><br></blockquote>
</blockquote>
<blockquote type="cite" cite>I would think that even in
single-threaded usage, if multiple RTSP client requests are required,
then the CSeq would still increase by more than one.</blockquote>
<div><br></div>
<div>Yes, and this probably does, indeed, violate the RTSP
specification. I originally made "fCSeq" a static
variable because I was worried about a server possibly getting
confused if the same CSeq value were used by two separate requests
from the same client host using the same URL - something that could
happen if fCSeq were made a (non-static) member variable. (Note
my comment in "liveMedia/include/RTSPClient.hh") In
practice, however, this is probably not going to be a problem for most
servers (because each request would use a separate TCP connection).
Therefore, because we have now seen a server that - instead - has
problems with the current implementation, I'll change it in the next
release of the software.</div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
http://www.live555.com/</div>
</body>
</html>