| commit | 97396ea81cf322ca6fe510a8ae2f1520abf33f25 | [log] [tgz] |
|---|---|---|
| author | martinduke <martinduke@google.com> | Fri May 02 14:10:14 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri May 02 14:11:29 2025 -0700 |
| tree | 6deae22deea1878ecfd5d93fa5f8ef357cf2e3cc | |
| parent | 4c6d4fb368e78f1e1a10ab7c6d4a50bba7a3accf [diff] |
Make incoming FETCH asynchronous to support going further upstream for objects. Today, when FETCH arrives, MoQT expects the application to tell it immediately if the data is available. Receiving MoqtFetchTask from the application is a signal that it is safe to send FETCH_OK. Change MoqtFetchTask to have both a FetchOkCallback and a FetchErrorCallback to facilitate delayed notification as the result of an upstream FETCH. This CL does not change the current outgoing FETCH model where MoQT does not deliver MoqtFetchTask to the calling application until FETCH_OK arrives. This is deferred to a later CL. It currently "works" but there ought to be a consistent API. PiperOrigin-RevId: 754128549
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.