[asterisk-dev] [Code Review] 3466: HTTP: Add TCP_NODELAY to accepted connections

[Joshua Colp]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/3466/#review11685
-----------------------------------------------------------



branches/1.8/main/http.c
<https://reviewboard.asterisk.org/r/3466/#comment21449>

    The other use of this uses "tcp" - is there any difference between that and tls? Do we need to choose one or the other based on the connection?


I think this deprecates the change Scott originally did when closing the connection.

- Joshua Colp


On April 18, 2014, 2:41 p.m., opticron wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/3466/
> -----------------------------------------------------------
> 
> (Updated April 18, 2014, 2:41 p.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> This adds the TCP_NODELAY option to accepted connections on the HTTP server built into Asterisk. This option disables the Nagle algorithm which controls queueing of outbound data and in some cases can cause delays on receipt of response by the client due to how the Nagle algorithm interacts with TCP delayed ACK. This option is already set on all non-HTTP AMI connections and this change would cover standard HTTP requests, manager HTTP connections, and ARI HTTP requests and websockets in Asterisk 12+ along with any future use of the HTTP server.
> 
> 
> Diffs
> -----
> 
>   branches/1.8/main/http.c 412564 
> 
> Diff: https://reviewboard.asterisk.org/r/3466/diff/
> 
> 
> Testing
> -------
> 
> 
> Thanks,
> 
> opticron
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20140418/a8f86087/attachment-0001.html>