Rodney Baker (12021-02-02): > Nagle can introduce unwanted latency which is not desirable for real-time > streaming. Mind you, tcp is inappropriate for real-time streaming anyway - > that's what rtsp was invented for. I don't think Nagle belongs at app level > anyway - it's a network stack function (that can be disabled with the > TCP_NODELAY setting).
I know all that. Please do not answer ONLY to the last sentence of my mail. You have not answered the important part: > > Can you clarify something? Is this supposed to be a packet protocol or a > > stream protocol? > > > > I.e., if the reader is waiting for 100 octets, and the writer sent 20 > > then 30 then 40, will the reader get three reads of 20, 30, 40 or a > > single read of 20+30+40=90? Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
