| commit | 137ec0c681557d0bea79e8d14a7361aa6a73202f | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Wed Aug 28 12:01:33 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Aug 28 12:02:37 2024 -0700 |
| tree | 0c31993c208ffb35dd89d1f25d4079d583865366 | |
| parent | d249e53db5364c7a67a8c51205f34e30f5562686 [diff] |
Introduce Object ACKs (OACKs) to MoQT. OACKs let the application receiver acknowledge that it has received (and potentially processed) the object. In addition to that, we also communicate how far off from the deadline the object was received. The sender want to know this information if it is in a position to adjust the send rate: - when it's a 1:1 connection and it controls the video bitrate, - when it's doing sender-side ABR. The reason we want to do MoQ-level ACKs is that the alternatives are not as good: - using QUIC ACKs directly breaks layering and is infeasible with web APIs - using a building up queue as a signal is possible, but the queue takes a time to build up, thus making it a delayed signal PiperOrigin-RevId: 668549384
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.