| commit | 42dab6be059fbe2a3d98367e1d5ad19d887156d3 | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Sun Feb 18 08:47:27 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Sun Feb 18 08:48:13 2024 -0800 |
| tree | eb57854ee05b1380dc718e28bd0fba6d02568ed8 | |
| parent | eb58cf09f4abfbd8388934464a85803c9cbb1a87 [diff] |
Refactor the framer and some of the publishing pathway for MOQT. Changes to framer: - Use wire_serialization.h API where possible. - Remove unused SerializeObjectPayload method. - Change SerializeObject into SerializeObjectHeader; we never want to copy the object payload here, since it almost always should be passed directly into the underlying stream using Writev. - Simplify some code paths (in case of SerializeObjectHeader at cost of repetition) in order to make them easier to read and modify going forward. Changes to PublishObject: - Always require full payload; we didn't really provide a way to write the remaining payload, and that would require a different API we could add later. - Check that end_of_stream is always set for Object/Datagram. PiperOrigin-RevId: 608134589
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.