Hi

After some flustration with blocking on dns requests while using the
multi interface with libevent (https://github.com/larroy/mycelium) I
investigated how curl uses ares and I came to the conclusion that the
design of asyn-ares.c is very limiting.

What's the point of having all the goodies of the multi interface to
use epoll etc, when waitperform function in asyn-ares.c just polls
waiting for DNS queries to finish?

I think the proper way would be to expose the resolving sockets up to
the multi interface so the whole system is really asynchronous. Is
there any reason why it wasn't done this way?

Regards.

Pedro.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-12-18