| commit | edc6d15283b202c75aa0fbb4e062a96a94f65afa | [log] [tgz] |
|---|---|---|
| author | QUICHE team <quiche-dev@google.com> | Mon Jun 23 12:34:40 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 23 12:35:35 2025 -0700 |
| tree | 71e834be9ee7a2d985dfd5069e84faf795ee51c0 | |
| parent | ac423eea2aafaa0da3d211702e0838b6c8971b20 [diff] |
Added the following experiments: 1) Testing different PTO values (2, 3 and 5) for path degradation. (cl/766276642) 2) Enabling multi-port connection creation on 1 RTO in PTO_MODE with and without migration. (cl/772554253) 3) Added the test in the `end_to_end_test` when both kMPR1 and kMPQM are passed in the client connection options. PiperOrigin-RevId: 774884978
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.