On Thu, 24 Jan 2013, Török Edwin wrote:

> I am using the curl multi interface and I see a lot of timeouts on slowish
> links (all fine on fast links of course). I have concluded that
> CURLOPT_CONNECTTIMEOUT sets not only the timeout for connect(), but also the
> timeout for starting to receive a reply for a pipelined request.

If that's so, then it is a bug. You didn't mention what libcurl version you're
using.

This said, Linus Nielsen Feltzing has a pretty massive HTTP pipelining patch
pending to get merged at some point after the 7.29.0 release so I'm reluctant
to fix anything pipeline-related until then. Possibly we should ask Linus how
to get his latest tree so that we can start trying out your problem on that
already now.

> Note: I'm actually interested in persistent connections only, not necesarely
> pipelining (that is just a nice addition), but in the multi interface I
> don't see a way to request that only: it is either both (MOPT_PIPELINING
> on), or neith (MOPT_PIPELINING off, separate connections).

Without pipelining it can't re-use the connections if you do multiple requests
in parallel. Without pipelining you need to issue the requests in a serial
manner if you want them to re-use connections.

Again, the pending work from Linus will allow some more customizibility in
this area as well.

-- 
  / daniel.haxx.se

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-01-29