On Tue, 21 Jul 2009, Nick Gerner wrote:

> Daniel, et al.: what's the impact of calling into the curl multi with a
> timeout even if the specified timeout hasn't expired?

libcurl will then simply not check any socket descriptors and only check its
existing timeouts, so if none of them has expired it will return again quite
quickly.

> All of that said, I've seen the timeouts inside curl work (giving a curl
> error of 28), even with CURLOPT_NOSIGNAL in most of my scenarios. Can you
> provide code?

The only timeout situation that libcurl uses signals for, is to timeout slow
name resolves when the synchronous system resolver is used.

-- 
  / daniel.haxx.se