Francis Cianfrocca wrote:

> > > libcurl offers an asynchronous API that does the name resolving
> > > asynchronously if you've built libcurl to do so.
> >
> > Does it use the native getaddrinfo()?  The problem I've had on FreeBSD
> > is that getaddrinfo() will block.

> Does it matter whether it blocks or not? Ruby can't schedule its green
> threads while you're inside a system-library call unless the call
> knows about Ruby's scheduler (which it doesn't). Right?

You _could_ read up on the libcurl details in the libcurl docs, but
then what fun would that be? Let's continue making assumptions like
this...

No, it is _not_ asynchronous inside a system call and it is _not_ using
the native getaddrinfo() for asynchronous name resolves.