On Thursday 29 January 2004 13:41, Daniel Stenberg wrote:
> On Wed, 28 Jan 2004, Dirk Manske wrote:
> > If ares and synchronous resolving in libcurl-7.11.0-pre1 is used no
> > resolve timeout is set. I've fixed that. The timeout is configurable.
>
> Two questions on this:
>
> 1. Doesn't ares have a default timeout if this isn't set like this?
Setting no timeout means endless.

> 2. Wouldn't it be enough to have a fairly long default timeout, and then
> acknowledge CURLOPT_TIMEOUT and CURLOPT_CONNECTTIMEOUT in case they're
> shorter than the default? I mean, is it really necessary to introduce
> yet another timeout?
For me it is not a must-have, so setting ares resolve timeout to
CURLOPT_CONNECTTIMEOUT would be sufficient.

-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
Received on 2004-02-02