| commit | 88d21fcd2a738dfea1c663a1630cd573e20a93ad | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Wed Jan 25 13:15:16 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 25 13:16:24 2023 -0800 |
| tree | d0160f5c1576c077467b3be10be22796285219e8 | |
| parent | 566b33c9fa5b1723db04be3d40dcaf102344c323 [diff] |
Implement a new API for serializing data into QUIC wire format. Also rewrite the Capsule serialization logic to use the new API. I started working on WebTransport over HTTP/2 capsules recently, and realized that the existing code requires too much boilerplate per capsule to be sustainable. This CL is an effort to reduce the cost of adding individual capsules. PiperOrigin-RevId: 504643109
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.