HTTP/2 support with OkHttp #428
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I extensively use Just Player for streaming DASH and when checking out my server's logs I found out that Player only use HTTP/1.1. HTTP/2 is already widely rolled out and brings many improvements especially on the performance side, so I seek out ways to give HTTP/2 support to Player. I found out that this can be done with changing the network stack, and ExoPlayer upstream provides 2 alternative network stack with HTTP/2 support: OkHttp and Cronet. Since Player already uses OkHttp, I chose to use it.
I use this guide to help me do this change.