| commit | a8e23fe0b5299c1984ce3355122c8e08e7c98be4 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Wed Apr 27 07:38:46 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 27 07:39:39 2022 -0700 |
| tree | 35767074060baf5e71dcddd8d77f33c746c514d0 | |
| parent | bc02673d9ea4937cfec65dee62e95a9fca31239b [diff] |
Make BalsaBuffer constructors public. Constructors should be private when there is a public factory method for creating the object, to prevent accidental instantiation not by the factory method. However, this is not the case with BalsaBuffer. This class is instantiated using its constructors by BalsaHeaders and in tests, and there making the constructor public allows the removal of a forward declaration, two friend declaration together with their comment, and another comment stating "this is awkward". Also while working on BalsaBuffer constructors, replace absl::WrapUnique(new) with std::make_unique<>. PiperOrigin-RevId: 444855708
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.