commit | a9c7837f7085662870031f8134f7464e56f1bb01 | [log] [tgz] |
---|---|---|
author | bnc <bnc@google.com> | Tue Nov 22 13:18:12 2022 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Nov 22 13:19:05 2022 -0800 |
tree | bf7de751c5facb273a02049fb477369c2a116f96 | |
parent | bc30c5a4857413fed6b9c0018968728ab9efdc0a [diff] |
Remove PrioritizedElementType. This was always REQUEST_STREAM when parsing, because HttpDecoder ignores frame type 0xf0701. It was also always REQUEST_STREAM when serializing, because HttpEncoder::SerializePriorityUpdateFrame() called QUIC_BUG if it wasn't. PiperOrigin-RevId: 490319696
QUICHE stands for QUIC, Http, 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.