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.

Sign up for GitHub

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

Jump to bottom

Use async-h1 for client by default #217

Open
3 of 5 tasks
Fishrock123 opened this issue Aug 16, 2020 · 2 comments
Open
3 of 5 tasks

Use async-h1 for client by default #217

Fishrock123 opened this issue Aug 16, 2020 · 2 comments
Labels
semver-major

Comments

@Fishrock123
Copy link
Member

Fishrock123 commented Aug 16, 2020 •
edited
Loading

Seems like a good time to discuss this, is this something that would be desirable for 2.0.0?

The List:

  • outgoing chunked encoding (done in async-h1)
  • compression
  • forwarding
  • connection pooling (done in http-client)
  • client timeouts

We are not aiming to get HTTP/2 compatibility at this time. Use the curl_client or hyper_client if you need that.
@Fishrock123 Fishrock123 added this to the 2.0 milestone Aug 16, 2020
Fishrock123 added a commit to Fishrock123/surf that referenced this issue Sep 7, 2020
@Fishrock123
Crate: export with the async-h1 client by default
9b5163a 
This should be stable enough.

Refs: http-rs#217
This was referenced Sep 7, 2020
Draft
Closed
@yoshuawuyts yoshuawuyts mentioned this issue Sep 7, 2020
Closed
7 tasks
Fishrock123 added a commit to Fishrock123/surf that referenced this issue Sep 8, 2020
@Fishrock123
Crate: export with the async-h1 client by default
c0362fc 
This should be stable enough.

Refs: http-rs#217
@Fishrock123 Fishrock123 removed this from the 2.0 milestone Sep 10, 2020
@Fishrock123
Copy link
Member Author

See the PR for further follow-up: #223

@yoshuawuyts yoshuawuyts mentioned this issue Dec 4, 2020
Open
@Fishrock123 Fishrock123 mentioned this issue Feb 12, 2021
Closed
8 tasks
@Fishrock123
Copy link
Member Author

timeouts will be done when #310 lands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
semver-major
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Fishrock123