On Wed, Nov 15, 2017 at 6:21 PM, Aman Gupta wrote:
>
>
> On Wed, Nov 15, 2017 at 2:35 AM, Jeyapal, Karthick
> 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
On Wed, Nov 15, 2017 at 2:35 AM, Jeyapal, Karthick
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 t
>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
On Tue, Nov 14, 2017 at 9:28 PM, Jeyapal, Karthick
wrote:
>
> >On 11/15/17, 10:32 AM, "Aman Gupta" wrote:
> >
> >From: Aman Gupta
> >
> >Signed-off-by: Aman Gupta
> >---
> > libavformat/http.c | 1 +
> > libavformat/tls.c | 1 +
> > 2 files changed, 2 insertions(+)
>
> Again, do want to hardcod
>On 11/15/17, 10:32 AM, "Aman Gupta" wrote:
>
>From: Aman Gupta
>
>Signed-off-by: Aman Gupta
>---
> libavformat/http.c | 1 +
> libavformat/tls.c | 1 +
> 2 files changed, 2 insertions(+)
Again, do want to hardcode tcp_nodelay at http and tls level? Because there
could be other muxers
that se
From: Aman Gupta
Signed-off-by: Aman Gupta
---
libavformat/http.c | 1 +
libavformat/tls.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/libavformat/http.c b/libavformat/http.c
index 056d5f6583..f0a80b7add 100644
--- a/libavformat/http.c
+++ b/libavformat/http.c
@@ -468,6 +468,7 @@ sta
