| commit | 7af2fb5eb2d791ed38efdfee8fc740077c5e4f6f | [log] [tgz] |
|---|---|---|
| author | danzh <danzh@google.com> | Fri Aug 29 14:34:19 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Aug 29 14:35:23 2025 -0700 |
| tree | 9f8b0bac4304c16766c5d1b582bab5f552b253b4 | |
| parent | 3af583d493739d25f5ec3c922890ef0fd23f8423 [diff] |
Support various migrations upon detecting path degrading: Perform early migration to a different network if allowed. Otherwise migrate to a different port if allowed. Otherwise do nothing. Also add logic to handle platform signal OnNewNetwork(). If there was an earlier attempt to migrate to a different network but it failed due to no alternative network available, try migrate again. This is part of the chain CLs to fork Chromium's connection migration code extracted in https://chromium-review.googlesource.com/c/chromium/src/+/5980615 which is verified to work for Chromium. PiperOrigin-RevId: 801032706
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.