On Mon, Mar 22, 2010 at 6:35 PM, Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com">finlayson@live555.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div class="im">
<blockquote type="cite">I've set breakpoints in every callback I
could find, after my doEventLoop() call, etc. When I kill my
internet connection mid-stream, I hit none of these breakpoints.
</blockquote>
<div><br></div>
</div><div>OK, it sounds like you're blocking in your RTSP client
"ANNOUNCE" operation. This will not be a problem in
the upcoming "RTSPClient" restructuring (that will make all
RTSP client operations asynchronous).</div></div></blockquote><div><br>Any idea when this might happen, and do you need any help? I definitely need these changes, so anything I can do to expedite that will be done.<br> <br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div class="im"><br></div><div>OK, so you would need to check for RTCP packets - assuming that
Darwin sends them; I don't know whether it does. If so, you
could do this using "RTCPInstance::setRRHandler()" (assuming
that Darwin sends RTCP "RR" packets in response to
"ANNOUNCE" data).</div><br></div></blockquote><div><br>I added a handler to check for RR reports, but unfortunately my server does not send them. I verified this on their forums as well (we're not using Darwin, but the general idea is the same).<br>
<br>So, I guess my only option is to modify the library to do a per-RTPInterface variable that tracks TCP failure. Would you have any interest in this change if I supplied a patch?<br><br>Thanks for your help.<br></div></div>