| commit | 10041054ccb96839beba7bb8a86a6aff16c01dd2 | [log] [tgz] |
|---|---|---|
| author | diannahu <diannahu@google.com> | Thu Jun 15 12:51:22 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 15 12:52:08 2023 -0700 |
| tree | 4def58f296ed93c95f0f00c881d1c112fff1d231 | |
| parent | 6df640d9ac49b76d01774bbb538cdc1d1f62193c [diff] |
Update the BalsaHeadersSequence internal data structure from std::list to absl::InlinedVector. The std::vector/absl::InlinedVector may be somewhat more performant by default overall, especially once we switch from BalsaHeaders to std::unique_ptr<BalsaHeaders>, which is planned for the next CL (cl/538578037). Some interesting discussion on this comparison is at https://stackoverflow.com/q/2209224. The std::vector/absl::InlinedVector is also somewhat easier to work with, though there is a fond farewell to `&*iter_++`. Inspired by http://google3/gfe/gfe2/http2/http2_writer.h;l=164;rcl=524908183 :D PiperOrigin-RevId: 540664124
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.