> -----Original Message-----
> From: curl-library-bounces_at_cool.haxx.se [mailto:curl-library-
> bounces_at_cool.haxx.se] On Behalf Of Armel Asselin
> Sent: Thursday, June 22, 2006 7:02 PM
> To: libcurl development
> Subject: Re: Anyone for HTTP Pipelining?
>
> > The priority setting P could be used in addition to L or instead of
L.
> If
> > libcurl has an important transfer it submits it with a high priority
and
> > libcurl will immediately (or after a period L) open a new connection
if
> no
> > connections are completely free. If a low-priority transfer is
> submitted,
> > libcurl would never open a new connection, but wait until all
> > higher-priority
> > requests are complete.
> if there is a priority stuff, one mandatory thing: order should be
> respected
> for equal priorities... not easy but for example when using WebDav
> MKCOL...
> you do not want the dependent HTTP PUTs to happen before it occurred
so
> they
> must be pipe-lined to the same connection or must wait for the
response.

The HTTP spec says that only idempotent requests such as GETs may be
pipelined. PUTs and POSTs cannot be pipelined.

Ravi.
Received on 2006-06-28