| commit | c17595a8831ed175cebc6659eea83e8e486ebde6 | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Wed Jan 04 14:49:41 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jan 04 14:51:23 2023 -0800 |
| tree | 347105bc97efc84e0c5225be7388e56cf0e9ad35 | |
| parent | 4bdfa810532a294befb8e8048318309dabd36bd8 [diff] |
Refactor WebTransport API to make it independent of QUIC. This moves web_transport_interface.h types into their own namespace and directory, removes dependencies on QUIC types, and cleans the API in a bunch of other ways (notably, adds more documentation). A notable functional outcome of this refactor is that we accept datagrams as string_views instead of memslices. For HTTP/3 use cases, this will typically reduce one copy, since we always copy the contents of the datagram while appending the stream ID. PiperOrigin-RevId: 499584983
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.