| commit | 0b343ee1f4fe3594ada42e12311678db00234fda | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Tue Jul 19 06:14:22 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jul 19 06:15:28 2022 -0700 |
| tree | 06c10ccaf5dfecbb0c59572cba5824bd98289419 | |
| parent | 4befc52f284c1ff85cd898b41c1fe7015417b00e [diff] |
Simplify signature of most HttpEncoder methods. Return std::string instead of returing length and using a std::unique_ptr<char[]>* outparam. This simplifies call sites, and takes advantage of small string optimization to avoid heap allocations for small frames or frame headers. Keep using QuicheBuffer for SerializeDataFrameHeader() because it allows a performance optimization that is unfortunately not available for other frame types. SerializeAcceptChFrame() will be changed in a separate CL. PiperOrigin-RevId: 461865044
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.