This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kristjan.jonsson
Recipients kristjan.jonsson
Date 2009-06-04.10:32:32
SpamBayes Score 0.00037539564
Marked as misclassified No
Message-id <1244111562.06.0.62559579479.issue6192@psf.upfronthosting.co.za>
In-reply-to
Content
It is useful to be able to disable the Nagle algoritm on socket 
connections from the TCPServer.  These are typically used by HTTP servers.

If combined with write buffering (setting RequestHangler.wbufsize = -1) it  
can make sure that http responses are not subject to Nagle/Delayed-ack 
delays.  Disabling Nagle in addition to providing the buffering is 
necessary to make sure that the final wfile.flush() arrives promptly, in 
case a previous flush occurred and the final flush is small.

A patch is provided.
History
Date User Action Args
2009-06-04 10:32:42kristjan.jonssonsetrecipients: + kristjan.jonsson
2009-06-04 10:32:42kristjan.jonssonsetmessageid: <1244111562.06.0.62559579479.issue6192@psf.upfronthosting.co.za>
2009-06-04 10:32:40kristjan.jonssonlinkissue6192 messages
2009-06-04 10:32:38kristjan.jonssoncreate