Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Feature Request] Support "h2c"
See original GitHub issueI know that okhttp now have already supported h2-prior-knowledge.
However, it is still inconvenient to use, because h2_prior_knowledge cannot be used with other protocols at the same time.
In my project, I use okhttp to access the REST APIs of other modules inside the project. Because the project will eventually be deployed on the intranet, there is no incentive to use https. At the same time, I need to use okhttp to access some external resources on the Internet. At this time, I have to instantiate two OkHttpClients. It is very inconvenient to always pay attention to which one to access which resource.
If okhttp supports h2c, it will be very convenient to be compatible with both h2 and http/1.1 servers.
And it also matches the spirit of okhttp that recommending only one OkHttpClient.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It’s sadly to hear that.
Because
http/2support binary data format, persistent tcp connections, multiplexing, and header compression and reuse,http/2will have a lower latency thanhttp/1.1and a higher throughput rate. So it will be the best companion for RPC. And for internal RPC,h2cis easier to deploy thanh2and has less stress on the hardware. For example, gRPC supports bothh2andh2c.