| commit | 3cc972c194ea4a0c740beb97a609775a3e8aa7f7 | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Mon Jul 17 07:56:14 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jul 17 07:56:51 2023 -0700 |
| tree | cfce3f091dae19f83f17567c9a6665b59ccf5343 | |
| parent | 638757dda721ce1f3c453f0b65c84b85fea52b87 [diff] |
Introduce a generic wrapper that allows accessing raw QUIC sessions via WebTransport API Protocols like MoQ are defined to operate both over WebTransport, and over QUIC directly. This API would allow the code for that to be written once. It will also help us migrate the remaining QuicTransport users away. PiperOrigin-RevId: 548690421
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.