| commit | cbb8ccacd2e4af4de151b3996e09130fbce04190 | [log] [tgz] |
|---|---|---|
| author | birenroy <birenroy@google.com> | Wed Jul 10 12:48:55 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 10 12:49:58 2024 -0700 |
| tree | b88ae40854a616588148e5799fc70256e4ae536b | |
| parent | c141463302548a81bdc25b22c012f08bb416224c [diff] |
Moves the remaining library targets from //third_party/spdy/core to //third_party/http2/core. These targets are widely used in google3, so I am leaving vestigial forwarding header files and build targets, and will migrate library users via Rosie CLs. Protected by refactoring, no functional change, not protected. PiperOrigin-RevId: 651120420
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.