| commit | 0020a2213f74142f9484768007496adba003bb6a | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Wed Feb 22 13:49:46 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Feb 22 13:50:39 2023 -0800 |
| tree | e2177ddf8c50b297a366bfe5d941e2a0b5816c3d | |
| parent | 0158571fa54b3a96bd022e9e6bdeb8cb2560b37f [diff] |
Respect incremental parameter in QuicWriteBlockedList. As a reminder, HTTP/3 streams have two priority-related parameters received from the clien in PRIORITY_UPDATE frames: urgency (int) and incremental (bool). Before this CL, the incremental parameter is ignored. Writes within an urgency bucket are batched: if the last stream with data written has more data to write, it will be written unless more than 16 kB has been written so far. After this CL, writes on non-incremental stream are are batched with no limit. This is because partial responses on incremental streams are not useful for the client, so if there is more data available, it should be sent before other streams of equal urgency. Buffering behavior of incremental streams is not changed. Protected by FLAGS_quic_reloadable_flag_quic_priority_respect_incremental. PiperOrigin-RevId: 511587715
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.