<div dir="ltr"><br><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><br></div></div></div></div>
<br><div class="gmail_quote">On 30 September 2016 at 17:49, Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> No I am not referring to those. I am referring to incomplete packet reads for RTCP packets.<br>
> Specifically where the flag "packetReadWasIncomplete" is set.<br>
<br>
</span>OK, so what specifically is your question?<br>
<br>
The incomplete packet reads are normal (i.e., not buggy) behavior when you’re reading a RTP/RTCP-over-TCP stream.  They simply indicate that the most recent read from the TCP socket didn’t get all of the data that was needed to complete the RTCP (or RTP) packet.  Subsequent reads from the TCP socket will finish getting the complete packet.  There is no known bug in this code.<br></blockquote><div><br></div><div>I meant that why would every alternate reads return 0 bytes read. Shouldn't the read be not performed at all? </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
<br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" rel="noreferrer" target="_blank">http://www.live555.com/</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" rel="noreferrer" target="_blank">http://lists.live555.com/<wbr>mailman/listinfo/live-devel</a><br>
</div></div></blockquote></div><br></div></div>