| commit | 42787587fa727712939629f8e83f3ea2749e83a2 | [log] [tgz] |
|---|---|---|
| author | martinduke <martinduke@google.com> | Fri Jun 20 14:07:24 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Jun 20 14:08:16 2025 -0700 |
| tree | 48024b02a406bc58a9c3ddef1003a5cb4cf02ee0 | |
| parent | ff02865c0da8530cc2ac9f38f2e30f992f9cac4a [diff] |
Enforce limit on total length of MoQT FullTrackName. Also, since the separation of Track Name and Namespace now appears to be stable, rework the classes to distinguish them, instead of having "FullTrackName" sometimes be a namespace and others a full name. PiperOrigin-RevId: 773836112
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.