On Tue, 23 Feb 2010, Beatriz Rojo Martin wrote:

> I have tested it, but it only allows pipelining in different TCP packets. Is
> there any way to force to use the same TCP packet to send several HTTP
> requests? I'm really interested in such scenarios.

Won't nagle/slow start at least often make the first few (two?) requests go
into the same IP packet?

If they're not, why is it a gain to _wait_ with the first request for a
possible future HTTP request to merge them into a single IP packet?

libcurl has no particular magic to merge stuff into different IP packets.
libcurl uses the socket API and lets the underlying network stuff split that
into packets. You can of course use various socket options to tell the stack
to work in alternative ways.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html