On Thu, 18 Sep 2008, Dan Fandrich wrote:

> creating processes within libcurl could still have the potential of messing
> up an unsuspecting app.

Yeps! :-(

I figure a first approach could be to add a #ifdef'ed version that can be
enabled with configure or similar, to allow for users to enable in case they
want to avoid the sighandler problems of the current approach (and absolutely
can't agree to using c-ares).

Possibly we could even make it only get used if enabled with a setopt() option
to prevent users from getting surprises... it seems the current problems
haven't hit many people as it has been done like this for many years, so
perhaps (some/many) people can live with the drawbacks?

-- 
  / daniel.haxx.se