Hi developers

We've already before touched the subject of libcurl's habit of using signals
to abort slow (name resolving to be exact) function calls.

It is bad when libcurl is used by multi-threaded programs, as signals can't
be safely used then.

Now, what's the best (short-term) cure for this problem?

Should we add an option that says NOSIGNALS or one that says MULTITHREAD or
should we just say that if use libcurl multithreaded, no timeouts should be
used?

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/