On 01/23/2013 09:27 AM, Daniel P. Berrange wrote: > On Wed, Jan 23, 2013 at 11:24:25AM -0600, Dan Williams wrote: >> On Wed, 2013-01-23 at 02:46 +0100, Lennart Poettering wrote: >>> On Mon, 21.01.13 10:25, Daniel P. Berrange (berrange@xxxxxxxxxx) wrote: >>> >>>>> The glibc maintainers don't seem to be against this idea and I am >>>>> willing to put time into design and implementation. >>>> >>>> Perhaps I'm misunderstanding what you're after, but doesn't "getaddrinfo_a" >>>> already provide an async version of getaddrinfo ? >>>> >>>> "Asynchronous Hostname Lookup API" >>>> http://www.akkadia.org/drepper/asynchnl.pdf >>>> >>>> That said I don't see the reverse - getnameinfo_a >>> >>> Brrrrh. It's designed around process signal delivery. I am >>> shuddering. >> >> Ew. Signals are not an event loop API. Signals are not an event loop >> API. Signals are not an event loop API. But apparently that's hard for >> some people to understand... > > I never claimed it was a nice API, just that it provides an async hostname > lookup capability already :-) The signal handler can write a packet into a pipe from the process to itself, and that can be hooked up to an event loop API. -- -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
