commit | f27dba402268a4fd259791e4f1de91a69d0ff56d | [log] [tgz] |
---|---|---|
author | diannahu <diannahu@google.com> | Wed Aug 03 16:10:08 2022 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Wed Aug 03 16:11:31 2022 -0700 |
tree | 75e21d1a525c85c6c46a5088ef1f433e44b4dd15 | |
parent | 1699cb2a7ab2e9b069909cd1b0624812b4503f64 [diff] |
Move NoopEncoderStreamErrorDelegate from qpack_decoder_test_utils to qpack_decoder. This migration is a prefactor for using NoopEncoderStreamErrorDelegate in production code, i.e., Http3MetadataManager. This CL is analogous to cl/464792267, except that we cannot/should not remove qpack_decoder_test_utils altogether because at least one test class there (TestHeadersHandler) is #included in two separate test files. Given that we cannot remove altogether, this CL does not migrate other classes in qpack_decoder_test_utils. PiperOrigin-RevId: 465172685
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.