| commit | 0cb3c512e762dbaa18f441fe3ebfbb3b8e02ac20 | [log] [tgz] |
|---|---|---|
| author | diannahu <diannahu@google.com> | Wed Jul 26 18:23:45 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 26 18:24:28 2023 -0700 |
| tree | 158bf5c53d20eaaac019f83011ee58f538110b6d | |
| parent | 16f86e8366809643bb62b87028c47ff4a8f11a25 [diff] |
Add BalsaFrame::EnableTrailers(). This CL introduces a new method BalsaFrame::EnableTrailers() that will lead to invoking BalsaVisitorInterface::OnTrailers() (from parent cl/549685397) with the parsed trailers (via std::unique_ptr). This method will eventually replace BalsaFrame::set_balsa_trailer(), which takes a non-owning pointer to a trailers object to be populated. This new way is arguably more in line with the interim headers flow and may enable HttpReader clean-up. PiperOrigin-RevId: 551371987
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.