| commit | 001724f953156ebd727448029a24499ca4ef0615 | [log] [tgz] |
|---|---|---|
| author | diannahu <diannahu@google.com> | Wed Jul 26 10:35:04 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 26 10:35:51 2023 -0700 |
| tree | 4d1512b1b493b149008d629b49aa37b0016d3883 | |
| parent | 043e5c45fc27199546c6004e9003306ae250061b [diff] |
Add an interface method for accepting trailers (with ownership) in Balsa. This CL introduces BalsaVisitorInterface::OnTrailers() to deliver trailers with ownership, with the eventual goal of replacing BalsaVisitorInterface::ProcessTrailers() that delivers a non-owning reference to trailers. The goal is to migrate [1] and move the trailers-processing logic to a callback in BackendResponder, somewhat simplifying HttpReader (more details in descendant cl/550634500). A stretch goal is to unconditionally deliver trailers and then store them in HttpRequestInfo only if the conditions in [2] hold true. [1] http://google3/gfe/gfe2/jetstream/http_reader.cc;l=353;rcl=547269861 [2] http://google3/gfe/gfe2/jetstream/backend_responder.cc;l=1119-1120;rcl=549171119 PiperOrigin-RevId: 551249347
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.