Sergio M. Ammirata, Ph.D. (12021-01-31): > For writing, the data you give librist, will go out "as is" > to the network with some added protocol overhead bytes (28 > bytes without encryption enabled and 36 bytes with > encryption enabled).
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? > To avoid your data being fragmented because of network MTU, > you should really limit the write size to what you want > your IP packets to be. For mpegts, for example, 1316 is a > good number to keep the overall packet size below the > typical internet MTU size of 1500 (1400 to be safe). It looks to me like reinventing the wheel that TCP had had years to make nicely round. Do we need to implement the Nagle algorithm? 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".
