| commit | 9158c29131373686714d7b0c55eb76c0bbc4ef99 | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Fri Jan 13 08:07:53 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jan 13 08:08:46 2023 -0800 |
| tree | d3b595514ffc81cba91a4f69a4be20c4c35fc51a | |
| parent | aba74ffb31ba77be0a7ffd7c981286b1aeaa28e0 [diff] |
Provide an abstract API for a stream that one can write bytes into. For QUIC, we have a QuicPacketWriter as an API for outputting all datagrams used by the QUIC connection; since encapsulated WebTransport (aka WebTransport over HTTP/2) has a single bytestream as an output, we need a similar type for that. This CL takes the existing WebTransport stream write API, cleans it up, and moves it into its own class. Notable changes to the write API: - Make it vectorized - Let it return a status object instead of simple true/false - Merge writing and sending fin into a single method, the same way as existing QUIC APIs work Parts of the old API are still kept around for compatibility with existing calls. PiperOrigin-RevId: 501849717
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.