| commit | 7f36faaf2ea03210122e800e9ac54838f3ec6e23 | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Tue Feb 14 06:49:29 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Feb 14 06:50:28 2023 -0800 |
| tree | c4cf7e56a8630136ee48c8c03027e62d772f3c8b | |
| parent | c90f95af7f0590b7c4f5a6cfba1eea1b6cc2a45e [diff] |
Allow setting flush=true on datagrams queued via the session datagram queue. Currently, we allow bypassing congestion control for the datagrams when those are written directly via QuicSession::SendMessage(); WebTransport (and all other users of HTTP/3 datagrams) write datagrams via the QUIC datagram queue, meaning that the users of that API cannot set the flush flag directly. This CL introduces such capability. PiperOrigin-RevId: 509514630
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.