| commit | 30045be320b5a72bd4a18e43e74c1a50a6a7f0c1 | [log] [tgz] |
|---|---|---|
| author | haoyuewang <haoyuewang@google.com> | Fri Apr 08 12:57:08 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 08 12:57:49 2022 -0700 |
| tree | 7c27ebf5a0bd8ef4ebfba0378cee62db9317a1dc | |
| parent | d0152cad77cb5c1b57ff2cd3180b8abbc092f638 [diff] |
Remove connection_option RVCM such that IETF QUIC connection migration is default on. We need more stats from AFE teams to verify the corresponding flag but it is good to exercise this flag early in the GFE canary. Protected by FLAGS_quic_reloadable_flag_quic_remove_connection_migration_connection_option_v2. PiperOrigin-RevId: 440432966
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.