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

Updated to use asynchronous io #23

Closed
driftluo opened this issue Mar 17, 2018 · 2 comments
Closed

Updated to use asynchronous io #23

driftluo opened this issue Mar 17, 2018 · 2 comments

Comments

@driftluo
Copy link
Owner

driftluo commented Mar 17, 2018

hyperium/hyper#1443

Currently, hyper 0.12 is waiting for the release of futures 0.2. Tokio has explicitly supported the work-steal thread pool.

I also hope that this crate can use features to select whether the client uses asynchronous mode, that is say that support synchronous and asynchronous at the same time, the default synchronization mode.

However, currently, Rust/Cargo doesn't support two versions of a library at the same time, which makes it very difficult for me to do it. Maybe 2018-epoch RFC can help me?

Maybe use reqwest? But it currently only supports uses system-native TLS....

Or wait for hyper 0.12 to give up sync mode directly?

@driftluo
Copy link
Owner Author

Oh, rust-lang/cargo#6319 this can allow me use two versions of a library at the same time, so cool

@marcelbuesing
Copy link

futures 0.3 (alpha) support was just added to the master branch of hyper. E.g. see this for an example of a client using Futures + await. I think it would be great to use this.

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

No branches or pull requests

2 participants