| commit | ab43084988b8ca73d30374b7030057fa18019589 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Mon Dec 12 09:47:35 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Dec 12 09:48:48 2022 -0800 |
| tree | 78cd1586054c677a33325a6e61d5cc5f1aa63a77 | |
| parent | 14c24a0197c308046d6121b54ec5ad358771f074 [diff] |
QuicStreamPriority refactor Create QuicStreamPriority class in a dedicated build target, move parsing and serializing functions and their tests together. Consolidate constants like minimum, maximum and default values, and structured header dictionary keys "u" and "i", and re-use them in both the parsing and serializing methods (previously ParsePriorityFieldValue() had these values hardcoded). https://github.com/google/quiche/issues/25 PiperOrigin-RevId: 494755193
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.