Decompose Client into utils
Open
Nobody has claimed this yet.
A-client
C-feature
E-medium
K-hyper-util
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
Besides a connector and pool, the Client from 0.14.x did many small things that should be decomposed into pieces in hyper-util, so users can choose to compose the parts they want.
- Create a
SetHostservice layer (could also fit intower-http) (0.14.x code) - Create a
Http1RequestTargetservice layer (0.14.x code) - Create a
DelayedReleaseservice layer (0.14.x code) - Create an
AutoConnectionwhich can wrap HTTP/1 and HTTP/2 (and eventually 3) connections
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 by reading the linked 0.14.x implementation in src/client/client.rs, then inspect the current hyper-util structure and consider whether SetHost belongs in tower-http. Done means the four checklist components—SetHost, Http1RequestTarget, DelayedRelease, and AutoConnection—are decomposed so users can compose the desired client parts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, networking
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100