commit | cb3863a8c4837ea98b48cb8d467adc22f2b937d1 | [log] [tgz] |
---|---|---|
author | bnc <bnc@google.com> | Fri Jun 24 10:59:29 2022 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 24 11:00:36 2022 -0700 |
tree | 27cd2ac117cfaede662a2adacd8e72df20e08b87 | |
parent | c06ea15fb70cf290667de767d9862ba8ef3a76e9 [diff] |
Add HttpEncoder::SerializeMetadataFrameHeader(). Add HTTP/3 SETTING_ENABLE_METADATA. Add HTTP/3 METADATA frame type. Add HttpEncoder::SerializeMetadataFrameHeader() method to serialize METADATA frame header. Setting identifier and frame type match HTTP/2 ones, see quiche/spdy/core/metadata_extension.cc. See https://github.com/envoyproxy/envoy/issues/2394 and design document linked therein for HTTP/2 METADATA. HTTP/3 implementation will be very similar. PiperOrigin-RevId: 457048873
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.