| commit | 4dfeec14eb632edfd26428ac69d3551f48f051ff | [log] [tgz] |
|---|---|---|
| author | ericorth <ericorth@google.com> | Fri May 31 09:39:12 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri May 31 09:40:48 2024 -0700 |
| tree | 022351e99ceabfe734cc343e29a8c2683b61b626 | |
| parent | 9fdc4b470136f659a6f40f382dc7f9be1981a63a [diff] |
Remove non-default initcwnd capabilities from Bonnet Functionality should no longer be necessary now that we have deprecated the partial message buffering in Arnold inspection, and was disabled by default and in run_bonnet in previous CLs. Startblock: cl/634555661 is submitted and then 2w have passed PiperOrigin-RevId: 639062841
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.