swagger-api / swagger-api/swagger-codegen
[swift] keep-alive not working
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
It looks like the way the Alamofire is implemented we loosing all of the keep-alive sessions because every request has it's own manager. Is there is a way to have keep-alive enabled that would greatly reduce latency on SSL connections. The code in question is this one https://github.com/swagger-api/swagger-codegen/blob/master/samples/client/petstore/swift/default/PetstoreClient/Classes/Swaggers/AlamofireImplementations.swift#L53
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 with samples/client/petstore/swift/default/PetstoreClient/Classes/Swaggers/AlamofireImplementations.swift at the referenced implementation. Inspect how each request creates or obtains its manager and review the issue discussion for existing conclusions. Done means Swift client requests preserve keep-alive sessions and avoid the reported loss of SSL connection reuse.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100