Skip to content

Use async-h1 for client by default #217

@Fishrock123

Description

@Fishrock123

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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions