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(client): change GaiResolver to use a global blocking threadpool #1917

Merged
merged 1 commit into from
Aug 29, 2019

Conversation

seanmonstar
Copy link
Member

BREAKING CHANGE: Calls to GaiResolver::new and HttpConnector::new no
longer should pass an integer argument for the number of threads.

@sfackler
Copy link
Contributor

Does the resolver interface need to exist at all anymore once TcpStream::connect does the resolution on its end?

@seanmonstar
Copy link
Member Author

Maybe TcpStream::connect gets smart enough, but for now, the connector stuff in hyper does more, like supporting happy eyeballs. Plus, with Resolve changed to a Service, one could easily use combinators to add in address blacklists/whitelists and things.

BREAKING CHANGE: Calls to `GaiResolver::new` and `HttpConnector::new` no
  longer should pass an integer argument for the number of threads.
@seanmonstar seanmonstar merged commit 049b513 into master Aug 29, 2019
@seanmonstar seanmonstar deleted the gai-blocking branch August 29, 2019 21:16
seanmonstar pushed a commit that referenced this pull request Sep 6, 2019
* test(http): use async/.await

Signed-off-by: Weihang Lo <me@weihanglo.tw>

* test(pool): use async/.await

* test(pool): pass &mut Future into PollOnce

* test(client): tests/benches using async/.await

* test(client): change due to PR #1917

* test(client): change Delay to delay fucntion

Ref: tokio-rs/tokio#1440

* test(client): remove warning triggers
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.

2 participants