| commit | b28dc0ca839d6623820e7272b619f37f3287d1b7 | [log] [tgz] |
|---|---|---|
| author | rch <rch@google.com> | Thu Oct 19 13:39:32 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 19 13:40:22 2023 -0700 |
| tree | d111de7f1b4490c20ca369744a7a40448468de08 | |
| parent | 646dbc0b871d59ccb94084e7c3842fb320e3e78b [diff] |
When quic_limit_sending_max_streams is enabled and MAX_STREAMS frame is ack'd, delay sending a new MAX_STREAMS frame if the connection is currently processing a packet. Protected by quic_reloadable_flag_quic_limit_sending_max_streams. PiperOrigin-RevId: 574987377
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.