swagger-api/swagger-codegen

[swift] keep-alive not working

Open

#4,333 opened on Dec 7, 2016

View on GitHub
 (9 comments) (0 reactions) (0 assignees)HTML (5,474 forks)batch import
Client: SwiftIssue: Bughelp wanted

Repository metrics

Stars
 (12,701 stars)
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

Research direction
Investigate the Alamofire implementation in the given file to understand why keep alive sessions are lost per request, and find a way to reuse the manager or session across requests to maintain keep alive connections.
Tech stack
swift
Domain
api
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
SwiftAlamofire
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75