[ldns-users] function call backs in ldns_resolver_send*?

[W.C.A. Wijngaards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hoi Miek,

On 12/15/2010 12:53 PM, Miek Gieben wrote:
> [ Quoting Wouter Wijngaards in "Re: [ldns-users] function call back"... ]
> True, but with callbacks you can fire off multiple requests and then
> wait for a reply from one of them.
> Currently this is hard to do because ldns_resolver_send* hides all this.
> 
> I'm not proposing to make ldns into a threaded library, we have
> libunbound for that, I'm asking for a way to seperate the send and
> receive in ldns.
> 
>> It is not viable (for ldns itself).  libunbound gives you a callback
>> that gives the packet wiredata from unbound, it handles the threads,
> 
> Do callbacks imply threads? (I thought not, but I may be wrong).

Well asynchronous implies threads.  You want something that resolves an
array of 5 queries at the same time, and it finishes when they are all done?

That is still a fair amount of work.

Best regards,
   Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk0IrmgACgkQkDLqNwOhpPgc0ACdEjkdGxJ1XgCAaLy6OF4L86Uh
dpMAoLNSBXNUdOgQUECp29zNyuudzqMK
=D7RB
-----END PGP SIGNATURE-----