Working on new thread pools for #curl to rework the async DNS resolving. This will be useful for performance and resource control, as well as improved happy eyeballing.
This all because simply calling ‚getaddrinfo‘ is not good enough and replacements like c-ares are never 100% compatible to all the quirks that exist „below“ getaddrinfo.
So, here we go.💃
(Writing threaded code always makes me feel real good about myself until it all blows up in my face. So, fun!😌)
@icing What would you list as "quirks that exist below getaddrinfo"?
I'm asking because I find that getaddrinfo is a terrible interface (worse than the libc average, which is saying a lot) and have written my own DNS library, including an interface for asynchronous resolution, and am curious whether you found the same flaws as I did or if your assessment is entirely different 😅
@pemensik @icing @ska c-ares has a plug-in replacement implementation for getaddrinfo() but still after some twenty years or so we have not managed to make it 100% compatible with glibc's version, which ultimately makes it not used by for example Linux distros as a resolver engine for curl.
But I will admit that by now it has been a few years since anyone did such test.
