Control over connection pooling?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.3k
- Forks
- 1.8k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 14
Description
Right now, it seems that connection pooling is interwired with the http client itself. Does that have to be the case? Would it not be possible to implement pooling with a custom connector instead?
I have a program that generates a lot of connections, even though it only ever connects to the same server. I need to investigate a little bit more, but I'm assuming right now that for some reason, it is losing the race with the pool checkout quite often.
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
No files, tests, or entry points are named. Start by tracing how the HTTP client and custom connector interact, then establish whether pooling can be separated and what behavior should be verified for repeated connections to one server.
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
- Needs clarification
- Newbie friendliness
- 25/100