On Fri, 10 Sep 2010, lali .cpp wrote:

> Does it mean that it makes no sense to set these two timeouts i.e
> CURLOPT_CONNECTTIMEOUT_MS and CURLOPT_TIMEOUT_MS on the easy handles when
> these easy handles will be used by adding them to a multihandle?

Correct, not until you use the version we now are working on in git.

> Anyway, to enforce transfer timeout in a multihandle, I can set timeout in
> select and then break out of the loop.

Well, a timeout in the select() is not the same thing, but you can still abort
the loop after a specified time, yes.

> Regarding the application crashes I am observing, they all occur because a
> "connectdata" structure being used is invalid. Does setting a timeout on
> easy handles removes the connection on timeout?

No

> This problem looks similar to
> http://www.mail-archive.com/curl-library@cool.haxx.se/msg04380.html except
> that I use http instead of ftp.

I doubt it is even similar, as that problem was due to the delayed kills we do
on some protocols, like FTP. We don't on HTTP. Besides, as we fixed that
problem you can just upgrade and see if your problem is gone.

> Can you please give me a brief as what is the result of using timeouts on
> easy handles when these handles would be used for transfer only in a
> multihandle?

There is no results at all. The options have no effect. Until you upgrade to
the next version that is.

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