On Wed, Nov 15, 2017 at 6:21 PM, Aman Gupta <a...@tmm1.net> wrote: > > > On Wed, Nov 15, 2017 at 2:35 AM, Jeyapal, Karthick <kjeya...@akamai.com> > wrote: > >> >Hmm, I guess if we want this to propagate down we need to add the option >> to the tls protocol as well, then pass it down when it instantiates the tcp >> protocol. Then add the same option to hls/dash, and again propagate it >> >down to tls or tcp. >> >> > >> >> >This is turning into a much bigger change than I anticipated, and I >> don't really care enough about it to continue. If someone else wants to >> take over this patchset, they are more than welcome to it. >> >> > >> >> >Aman >> >> >> >> Well, I would suggest you could push the first tcp patch and leave the >> http/tls patch for somebody else to take it up later. >> > > That's fair. > > I've tested compiling the change on windows (w/ mingw), freebsd, linux and > macOS. I hope there are no other obscure supported platforms where > TCP_NODELAY might not be defined? >
I've pushed the change to add the tcp_nodelay option to the tcp protocol. The second patch to use it from http/tls has been abandoned. Aman > > Aman > > >> >> >> Regards, >> >> Karthick >> > > _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel