Re: Anyone for HTTP Pipelining?
Date: Wed, 28 Jun 2006 22:21:50 +0100
Daniel Stenberg wrote:
> >>- Have an option like "attempt pipelining" and then it _may_ use that
> >>if an existing connection is already present against our target HTTP
> >The thing is that it is pretty hard for Curl to decide what to do based on
> >response length and it is probably best to leave this to the application.
> >Since pipelining is per multi handle, the application can always use a
> >different multi handle when it doesn't want a large request to interfere.
> Yeps. I didn't mean it would base it on the response lengths or anything, I
> just meant that when an application says to libcurl that it may use
> pipelining for requests, the effect may be that a previous big slow
> transfer will delay the latter small fast transfer quite significantly. But
> of course, with some nice info text about the pipelining status, just
> enabling verbose will reveal this information.
Fwiw, Mozilla allows HTTP requests to have different priorities.
I'd guess that means it's a useful feature.
Received on 2006-06-28