On Thu, 27 Mar 2003, Rick Jones wrote:

> Typically, if disabling Nagle improves throughput for an HTTP* transaction,
> it suggests that logically-associated data (ie the request or the response)
> is being given to the transport in separate send calls.

The GET request is sent in one big chunk. POST requests, however, are sent in
multiple requests (with the headers in the first, and the body in one or more
sends).

If I'm not forgetting things, that is.

> The discussion gets a bit more complicated once we are talking about
> _pipelined_ requests (versus persistent), but as I recall, libcurl isn't
> doing pipelined just yet.

Correct. It still doesn't do it.

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en