Max parallel requests per domain using h2 configuration option
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem? Please describe.
I have many concurrent requests most of them going to one domain. Hyper multiplexes them onto one physical connection. This connection has bandwidth limit. I have no ability (except creating new connection for each request) to define a number of maximum parallel connections for domain name.
Describe the solution you'd like
add option in ClientBuilder to define max_concurrent_requests_per_domain or similar)
Describe alternatives you've considered
Create new client for each request (limiting only one request per connection) - has higher overhead
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the ClientBuilder entry point and trace how Hyper multiplexes concurrent requests and manages connections for one domain. Define and validate the behavior of a max_concurrent_requests_per_domain option, including the existing connection-per-request alternative; done means the configured limit is respected without requiring a new client per request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100