[FFmpeg-devel] [PATCH] libavformat: add librist protocol
Nicolas George
george at nsup.org
Mon Feb 1 16:45:09 EET 2021
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20210201/96338e12/attachment.sig>
More information about the ffmpeg-devel
mailing list