| commit | bb8ac619a1e6563a94cf2abd0e59df9d795fa8a3 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Mon Dec 12 12:07:47 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Dec 12 12:09:27 2022 -0800 |
| tree | 8667c7e6792764983d2409e2f5df4743cc93f8ea | |
| parent | ab43084988b8ca73d30374b7030057fa18019589 [diff] |
Plumb QuicStreamPriority through QuicStream and QuicSession. No functional change still: the RFC9218 urgency has the same range as SPDY priorities (0 to 7 inclusive), so they can be used interchangeably, and RFC9218 incremental bit is always set to false in production. Note that this CL adds the capability to send PRIORITY_UPDATE frames with incremental bit set to true. This is not used in production, and in practice the server does not send PRIORITY_UPDATE frames anyway. However, this CL will allow Chrome to send such frames. This CL does not touch methods used for Google QUIC HEADERS and PRIORITY frames on the headers stream, because they use SpdyStreamPrecedence directly. These calls will eventually be removed with gQUIC. QuicWriteBlockedList changes will follow in a separate CL. https://github.com/google/quiche/issues/25 PiperOrigin-RevId: 494791164
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.