Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Is HTTP/1.1 Request Pipelining supported #1893

Closed
passsy opened this issue Oct 2, 2015 · 4 comments
Closed

Is HTTP/1.1 Request Pipelining supported #1893

passsy opened this issue Oct 2, 2015 · 4 comments

Comments

@passsy
Copy link

passsy commented Oct 2, 2015

I have to communicate with very limited hardware which supports only a few concurrent connections. I can work around this limitation with http pipelining which will be fully supported.

There is only one problem:
OkHttp doesn't seem to support http pipelining. Will this be supported in the future?
@swankjesse
Copy link
Member

No, we aren't planning on supporting HTTP pipelining. It’s not robust.

@inder123
Copy link

inder123 commented Apr 4, 2016

@swankjesse what do you mean HTTP pipelining is not robust? Pipelining should help in poor bandwidth connections in many countries. How would I go about enabling it in OkHttp?

@inder123
Copy link

inder123 commented Apr 4, 2016

https://github.com/jasondevj/hotpotato seems to support pipelining and is under Apache license. May be we can borrow something from there?

@swankjesse
Copy link
Member

They disabled it from Chrome because it performed poorly.
https://www.chromium.org/developers/design-documents/network-stack/http-pipelining

The workaround is HTTP/2.

@atiratree atiratree mentioned this issue Mar 29, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@swankjesse @inder123 @passsy