| commit | af960357cc5a874b2c379989379593a6151a02f5 | [log] [tgz] |
|---|---|---|
| author | ianswett <ianswett@google.com> | Mon Oct 04 12:23:11 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 04 12:24:00 2021 -0700 |
| tree | ae778db32828adc32012889f5ab263182e0822b5 | |
| parent | d61f11c9f8ac38cfc40559be24a6c30ec2d3e741 [diff] |
In BBRv2 STARTUP, exit after the same number of loss events(2) as PROBE_UP when the B206 connection option is supplied. Protected by quic_reloadable_flag_quic_bbr2_startup_probe_up_loss_events. PiperOrigin-RevId: 400785473
QUICHE stands for QUIC, Http/2, 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.