| commit | 3e9e5883670705703a3e5e3d083f1b0640c8aafc | [log] [tgz] |
|---|---|---|
| author | martinduke <martinduke@google.com> | Mon Aug 07 16:13:29 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Aug 07 16:15:02 2023 -0700 |
| tree | 78d30470d779cfc42aecd46ded816fcf22b795e8 | |
| parent | fddb3d0d3493de491b2079930f89a314f6fc8c0a [diff] |
Use three bits of Connection ID to indicate config. Connection IDs generated by LoadBalancerEncoder and QuicSiloIndexEncoder are never used in production, because we do not load any configs. Thus, the only part that needs to be flag-protected is the number of '1' bits added to the front of HASH_QUIC connection IDs (in CombinedConnectionIdGenerator). Protected by FLAGS_quic_restart_flag_quic_3bit_config_id. PiperOrigin-RevId: 554623294
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.