| commit | 5370f556f34f9a020877dad35ce263ef5be10156 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Wed Jul 13 10:15:16 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 13 10:19:06 2022 -0700 |
| tree | feca0069d64e9f34d36a83a42fd79fe45ed255da | |
| parent | 8af58e5779e2684d2ee3af8b7a7e234f7d29d9e7 [diff] |
Remove FrameSequence and MetadataSerializer. FrameSequence is an interface only implemented by MetadataFrameSequence (in anonymous namespace). Remove the interface and make MetadataFrameSequence public. MetadataSerializer is a trivial class with no members and only one factory method that creates a MetadataFrameSequence on the heap. Remove that class. Also remove the factory method. Change call sites to instantiate MetadataFrameSequence on the stack instead of the heap. PiperOrigin-RevId: 460745625
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.