| commit | 7eb7855461371d4d98e18a3d3e79895dd3f68c0e | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Thu Mar 10 12:41:26 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 10 12:42:09 2022 -0800 |
| tree | d6c5a1aa70e30c05288e43a502e4108cfa6c4cc0 | |
| parent | fdbf7def068fb69e8da1317ff8f297bd94ba0243 [diff] |
Ensures proper queuing of requests when too many are in flight. An Envoy integration test demonstrated that in particular circumstances, the oghttp2 library dequeues requests in the incorrect order, leading to interop problems when stream IDs do not monotonically increase. I verified that the included test case fails at HEAD, and succeeds with this change. Before: http://sponge2/fb9f0a8c-b2d9-4391-acf8-2f7e85abc372 After: http://sponge2/99574d9f-63f0-45e5-b1af-880bc055280d PiperOrigin-RevId: 433825658
QUICHE stands for QUIC, Http/2, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.