On Fri, 9 Mar 2007, Pedro Larroy wrote:

> After observing that resolution failures don't make the socket to get an
> event out of the multiplexer, I noticed that the documentation says:
>
> "Applications should call curl_multi_timeout(3) to figure out how long to
> wait for socket actions - at most - before doing the timeout action: call
> the curl_multi_socket(3) function with the sockfd argument set to
> CURL_SOCKET_TIMEOUT."

Hm, I believe that part of the doc is outdated. You should rather use the
CURLMOPT_TIMERFUNCTION option to curl_multi_setopt() to get timeouts on
particular sockets.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html