Open
Conversation
Author
|
You might want to break out the features and choose reqwest, hyper, awc, and tls based on features instead of using this PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Switch to using a recent version of awc on an actix_rt
Realistically, I plan on using this with an actix deployment, there is no reason to use hyper or reqwest.
One of the focuses of #24 was compile time, a
cargo clean && cargo build --release --example simple_sendertookand a
cargo clean && cargo build --release --example simple_sender --features opensslHere are the some of the features available on awc
I set the default feature
rustls, since we need SSLThis change is