On Mon, Aug 12, 2013 at 12:20:28PM +0200, Alessandro Ghedini wrote:
> On lun, ago 12, 2013 at 09:35:00 +0100, Paul Howarth wrote:
> > On 11/08/13 18:41, Alessandro Ghedini wrote:
> > >Hi all,
> > >
> > >lately I've been seriously thinking about switching to an asynchronous resolver
> > >for the Debian libcurl packages. There's a long-lived bug report asking to
> > >enable c-ares support (it was actually enabled a while ago, but because of the
> > >IPv6 bug it was later disabled), but AFAICT c-ares does not support the Name
> > >Service Switch (NSS) thingy, and there's probably no hope in adding support for
> > >it (unless making c-ares not asynchronous anymore...).
> > >
> > >So I've been playing with the threaded resolver and it seems to work fine, but
> > >I was wondering if any of you has had any problem with it that I should be
> > >aware of, considering that libcurl is one of the most installed packages in
> > >Debian.
> > >
> > >Comments?
> >
> > We've been using the threaded resolver in Fedora since Fedora 12 (4
> > years ago) and it looks pretty stable to me.
>
> Great, thanks! I'm going to enable it in Debian too then.

I had problems with threaded resolver. While it works fine in "good" network,
it sometimes hangs, especially if resolver runs when there is some network
problems. In my application I had to switch to c-ares eventually, I found no
possibilities to workaround this bugs in threaded resolver.

You can google about curl_multi_remove_handle() function, how it blocks during
dns work.

Here, for example:
http://comments.gmane.org/gmane.comp.web.curl.library/35514

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-08-30