|author||martinduke <email@example.com>||Wed Feb 09 10:16:34 2022 -0800|
|committer||Copybara-Service <firstname.lastname@example.org>||Wed Feb 09 10:17:48 2022 -0800|
Roll-forward support for QUICv2 after a more thorough inventory of ALPN impacts. Automated g4 rollback of changelist 427037417. *** Reason for rollback *** Restore support for QUICv2 after a more thorough inventory of ALPN impacts. *** Original change description *** Rollback for 4 changelists related to QUICv2. *** Reason for rollback *** Rollback QUICv2 until we figure out the impact on Chrome. *** Original change descriptions *** Fix C++ defensive coding advice from the QUICv2 CL (cl/424961568). There is much more to be done, but that could get out of control fast. Let me know if you want to abandon this, push more into this CL, or commit as-is. This CL restores QUICv2 support after auditing the effects of shared ALPN. *** Fix Intermittent Contagion Test failure. Since version mismatch is known to fail ungracefully, the... *** PiperOrigin-RevId: 427504970
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.