I noticed that the error code returned when the synchronous host
resolver times out is the same as when it can't be resolved at all:
CURLE_COULDNT_RESOLVE_HOST. But when the timeout proposed to be set is shorter
than a second (so a timeout can't be set) or if a previously-set alarm
couldn't fire because the resolver was busy, the error returned is
CURLE_OPERATION_TIMEDOUT. The latter code is also what's returned when a
connect can't complete due to reasons other than the host resolver.

Was this distinction being made deliberatly? I would have expected a
resolver timeout to return CURLE_OPERATION_TIMEDOUT in each case above.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved