Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Curl resolver threaded fix lag #112

wants to merge 5 commits into from


Copy link

commented Aug 21, 2014

This is actually on top of PR #111

The resolver thread occasionally gets stuck in getaddrinfo() when the DNS or anything else is crappy or slow, so when a host is found in the DNS cache, leave the thread alone and let itself cleanup the mess.

m6w6 added 5 commits Aug 20, 2014
cache lookup for async resolvers
the threaded resolver is a stubborn sheep though,
it still sits there and waits 5 seconds to complete
100 resolves
Rework Curl_fetch_addr docs
The docs reflected the first implementation; updated to reflect the end result.
fix the threaded resolver stuck in getaddrinfo()
don't know how well that plays on Windows, though

This comment has been minimized.

Copy link
Contributor Author

commented Aug 21, 2014


This comment has been minimized.

Copy link

commented Aug 31, 2014

Thanks, merged and pushed now (as a single squashed commit)

@bagder bagder closed this Aug 31, 2014

@m6w6 m6w6 deleted the m6w6:curl_resolver_threaded_fix_lag branch Aug 31, 2014

@lock lock bot locked as resolved and limited conversation to collaborators Jan 20, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.