Reusing the connection pool when cloning a client
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.9k
- Forks
- 409
- Avg merge
- 6h 47m
- Merged PRs (30d)
- 7
Description
I am writing an app that need to use different clients for different goroutines (so for example, requests to same sites with different accounts will be possible because different clients use different cookiejars). So I need to clone the orginial client for each goroutine but the problem is when cloning the client, the transports are cloned too with a new connection pool and it is a big waste of resources because if I have 200 goroutines, there will be 200 connection pools to be created.
Contributor guide
No contributing guide indexed for this repository
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 or tests are named. Start by locating the client-cloning path and transport or connection-pool construction, then determine how cloned clients can keep separate cookie jars while reusing the pool. Done means clients for different goroutines retain independent cookies without creating redundant connection pools; add or update coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100