Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Enable HTTP pipelining on iOS #3647

Closed
kkaefer opened this issue Jan 21, 2016 · 4 comments
Closed

Enable HTTP pipelining on iOS #3647

kkaefer opened this issue Jan 21, 2016 · 4 comments
Labels
iOS Mapbox Maps SDK for iOS performance Speed, stability, CPU usage, memory usage, or power usage

Comments

@kkaefer
Copy link
Contributor

kkaefer commented Jan 21, 2016

The default is set to NO

/cc @1ec5

@kkaefer kkaefer added iOS Mapbox Maps SDK for iOS performance Speed, stability, CPU usage, memory usage, or power usage labels Jan 21, 2016
@kkaefer
Copy link
Contributor Author

kkaefer commented Jan 21, 2016

This might explain why cURL is faster than NSURL*

@jfirebaugh
Copy link
Contributor

It sounds to me like HTTP pipelining is too new/dangerous to use. If the server you're connecting to (or proxy you're connecting through) doesn't implement it, you can get incorrect results without warning.

http://stackoverflow.com/questions/14810890/what-are-the-disadvantages-of-using-http-pipelining

@kkaefer
Copy link
Contributor Author

kkaefer commented Feb 9, 2016

Interesting, I thought it was accepted standard practice, but apparently not.

@friedbunny
Copy link
Contributor

iOS 9 and OkHTTP both have HTTP/2 enabled by default, which implements multiplexing. When Mapbox content servers start supporting HTTP/2, we should get it for free.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
iOS Mapbox Maps SDK for iOS performance Speed, stability, CPU usage, memory usage, or power usage
Projects
None yet
Development

No branches or pull requests

3 participants