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

feat(dns): tokio_threadpool::blocking resolver #1678

Merged
merged 1 commit into from
Oct 23, 2018

Conversation

sfackler
Copy link
Contributor

Unlike the default resolver, this avoids spawning extra dedicated
threads but only works on the multi-threaded Tokio runtime.

Closes #1676

Unlike the default resolver, this avoids spawning extra dedicated
threads but only works on the multi-threaded Tokio runtime.

Closes hyperium#1676
@seanmonstar seanmonstar merged commit 1e8d643 into hyperium:master Oct 23, 2018
@seanmonstar
Copy link
Member

Awesome, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Consider a Resolver that uses tokio-threadpool::blocking instead of futures-cpupool
2 participants