commit | bd94ccb9bdbc1530db3b61ebbd5deb4d356bd1bc | [log] [tgz] |
---|---|---|
author | bnc <bnc@google.com> | Wed Oct 20 09:18:49 2021 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 20 09:20:07 2021 -0700 |
tree | 9d64b94ae878c752a5f1711e59082d634b4f72d0 | |
parent | d05e8834b09739323c36ecd78642082204d2d07e [diff] |
Exercise Flush() in QpackEncoderStreamSender fuzzer. Also, remove TODO to feed data to a QpackEncoderStreamReceiver with a mock Delegate and add EXPECT_CALLs for each instruction. Mock objects are expensive to instantiate, and fuzzer targets need to be very fast in order to be effective. QpackEncoderStreamReceiver is fuzzed by its own fuzzer. PiperOrigin-RevId: 404563168
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.