This month's Index
Subject: recursive MX lookup <-> libc-ares <-> libev
recursive MX lookup <-> libc-ares <-> libev
From: Wilfried Goesgens <dothebart_at_citadel.org>
Date: Sat, 08 Jan 2011 10:00:37 -0500
I'm trying to evolve citadel.orgs smtp client to become async.
My toolchain of choice became c-ares and libev.
My current workstate can be found here:
For finding out the host needed to connect I need to do two DNS-calls in
I've managed to implement the MX lookup by inspecting the nodejs.org
My journey starts like this:
its setting* ares_init_options() *with a *SockStateCb()* and then sends out
ngrep shows, my query goes out, *SockStateCb() *is called, it registers the
My query-cb *DNS_io_callback()* gets invoked by libev, and calls
It then calls my application code, which then should resolve the IP of that
*ares_gethostbyname(Channel*/*(same as the last query)*/*,
I can then see the first a-query go out from within ares_gethostbyname(), the
when stepping out of it, back through my application call, back into c-ares,
If I don't step through it, the query for the IP just goes out once, but I
I'm also a little bit puzzled, that my IO-callback isn't called for sending
Any hints what I'm doing wrong here? Where should I look at?
TIA, Wilfried Goesgens