| commit | 75266116f21731354fe44cea6a1aae7eae70441e | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Tue Sep 26 17:29:55 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Sep 26 17:31:55 2023 -0700 |
| tree | 7002fc8fa1f7f367ea2c75a86fa6e005901cba6b | |
| parent | df3c6e7f4dab940a32b889080a6d535ea16f9431 [diff] |
Refactor the read part of WebTransport Stream API into ReadStream. The following changes are included: - Read()/ReadableBytes() are now a part of their own interface. - Introduce PeekNextAvaliableRegion()/MarkConsumed() as a zero-copy alternative to read. - Introduce a utility method for to use the peek API while taking care of reading FIN correctly. - Make webtransport::Stream a direct subclass of TerminableStream to avoid diamond inheritance problem. The long-term plan here is to abstract multiple kinds of streams for the goals of public APIs, including incoming QUIC streams, incoming WebTransport streams, and incoming HTTP request/response bodies. PiperOrigin-RevId: 568695001
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.