| commit | 7c0ef5f55e38c17cb5d181f8ca74e2925602c78c | [log] [tgz] |
|---|---|---|
| author | danzh <danzh@google.com> | Thu Jun 08 12:10:35 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 08 12:11:24 2023 -0700 |
| tree | 49393f2b3c96f5e6f03d1a6b8cd6870cef102306 | |
| parent | c0d96f53727670856cf26e6f5909f1cfdf6641f0 [diff] |
Deprecate flag --gfe2_reloadable_flag_quic_connection_migration_use_new_cid_v2. Make IETF compliant connection migration behavior depend on QUIC version instead of the reloadable flag. Removed QuicConnection::connection_migration_use_new_cid(). To QUICHE mergers, if it is called anywhere outside of QUICHE, replace it with version check, i.e. version_.HasIetfQuicFrames(), and remove the unreachable code if its call site is only reachable under IETF version today. PiperOrigin-RevId: 538855777
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.