| commit | 2235ac539088d722d77b0a73c627c9c364da3c21 | [log] [tgz] |
|---|---|---|
| author | bnc <bnc@google.com> | Wed Oct 20 11:27:26 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 20 11:28:24 2021 -0700 |
| tree | b42aaebea4195b3d9dde3a20d67225e8837dbff5 | |
| parent | bd94ccb9bdbc1530db3b61ebbd5deb4d356bd1bc [diff] |
Remove QPACK fuzz corpora. The fuzzing codelab makes the following recommendation: "Do not include in the build rule corpus tests that were generated by the fuzzer running locally. This is unnecessary, as the fuzzing infrastructure will automatically and transparently preserve and reuse the corpus generated by fuzzer runs." Since I generated all files in the corpus by running the fuzzer locally, they should not be checked in. PiperOrigin-RevId: 404599498
QUICHE stands for QUIC, Http/2, 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.