| commit | 63de6d9307e23aa9218edaa6b365f2f23b101c58 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Fri Jun 28 06:41:02 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 28 06:41:52 2024 -0700 |
| tree | 51d3de645f93ca2fcd760127436294d52500bf2c | |
| parent | 7f7fb05199101852596be2cd64d64b0ce635b731 [diff] |
Make default impl use quiche_feature_flags_list.h instead of quic_flags_list.h. The two files list the exact same flags, except the name prefix is different (quiche_ versus quic_), therefore the global variable used to implement the flags will have a different name. The second value in quiche_feature_flags_list.h is the same as the only value in quic_flags_list.h. This CL should therefore not result in any behavior change. The default flag implementation is only used in Chromium, and I already prepared a CL necessary to roll this QUICHE change. PiperOrigin-RevId: 647660906
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.