| commit | 9b5aac9172d4a50b53b557c86ee7715cf70740d1 | [log] [tgz] |
|---|---|---|
| author | vasilvv <vasilvv@google.com> | Wed Aug 17 15:21:41 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Aug 17 15:23:18 2022 -0700 |
| tree | 0eeb21c97fc0d2c56a1feb6fa9a7ef8934d22960 | |
| parent | 43e72e91e8c7e7bf9045375b9613ebaf576d0cc6 [diff] |
Partial rollback of cl/467313603 to unblock Chromium merge quic_toy_server is currently used as a basis for Chromium version of quic_server, and thus cannot depend on QuicEventLoop API (which currently works only on POSIX). PiperOrigin-RevId: 468306591
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.