▲ | blaz0 3 days ago | |||||||
I'm the author of the GitHub issue that the blog links to, and I'd like to thank Stefan for quickly acknowledging the problem and addressing the issue! I try to keep one of our internal applications up to date with the latest libcurl version within a day or two of a release, so we sometimes hit fresh problems while running our battery of tests. Ironically, our application has also struggled with blocking DNS resolution in the past, so I appreciate the discussion here. In case anyone is interested, here is a quick reference of the different asynchronous DNS resolution methods that you can use in a native code application for some of the most popular platforms:
| ||||||||
▲ | somat 2 days ago | parent | next [-] | |||||||
If we are doing a survey. I found a few more. It feels like we need to get everyone together in a room and say "we will let you out when you decide on a standard non-blocking address lookup" What a mess.
| ||||||||
▲ | jnwatson 2 days ago | parent | prev | next [-] | |||||||
As the article mentions, why not just delegate it to a library dedicated to the solution? c-ares is a solid, well-maintained library. | ||||||||
| ||||||||
▲ | wolletd 2 days ago | parent | prev [-] | |||||||
This information about `getaddrinfo_a` should probably also be in the Github issue? |