|author||dschinazi <firstname.lastname@example.org>||Fri Oct 29 15:18:38 2021 -0700|
|committer||Copybara-Service <email@example.com>||Fri Oct 29 15:19:41 2021 -0700|
Support draft-ietf-masque-h3-datagram-05 This revision makes datagram contexts optional to implement and negotiated via the Sec-Use-Datagram-Contexts header. See the PR for full details: https://github.com/ietf-wg-masque/draft-ietf-masque-h3-datagram/pull/105 This CL retains backwards compatibility with draft-ietf-masque-h3-datagram-04 by keeping support for the previous DATAGRAM capsule, which is now renamed to LEGACY_DATAGRAM. In this CL, our WebTransport implementation does not request support for contexts, so they will not be used for WebTransport. This code isn't used in our servers and therefore does not require flag protection. PiperOrigin-RevId: 406461234
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.