| commit | 69b700b7bde9ab8253f1c08ac6485da423366a65 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Wed May 11 09:24:44 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed May 11 09:25:34 2022 -0700 |
| tree | e9e97c3666f909dd819e648ca137ae0ea32c06a0 | |
| parent | 698178e8092a9c00e96015307fe5d7fbb844996b [diff] |
Add code count to support verification of quic_fix_on_stream_reset flag. Flag count for gfe2_reloadable_flag_quic_fix_on_stream_reset is zero. I believe this is due to the code path never executing on our servers. This change adds a QUIC_CODE_COUNT in the common path (regardless of the value of the flag) to measure fleet-wide execution, so that an informed decision can be made about verifying this flag. This is similar to cl/359286289 PiperOrigin-RevId: 448012287
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.