Rename QuicheTest implementation to QuicheTestImpl.

This is for consistency with the rest of QUICHE platform, and will also allow
moving QuicheTest (the API, not the impl) from the top level namespace to
quiche::test:

quiche::test::QuicheTest -> quiche::test::QuicheTestImpl (this CL)
::QuicheTest -> quiche::test::QuicheTest (future CL).

Unfortunately this means that after this CL temporarily there will be no
quiche::test::QuicheTest, hence the change in spdy_framer_test.cc that will need
to be reverted when QuicheTest is moved to quiche::test namespace.

To roll this to Envoy, this will require s/QuicheTest/QuicheTestImpl/ at
https://github.com/envoyproxy/envoy/blob/633d190b31ad954fd9250639087ba9772b42df12/test/common/quic/platform/quiche_test_impl.h#L30

To roll this to Chromium, this will require s/QuicheTest/QuicheTestImpl/ at
https://source.chromium.org/chromium/chromium/src/+/main:net/third_party/quiche/overrides/quiche_platform_impl/quiche_test_impl.h;l=20;drc=ea4fa1900a488bdc0c65d6147f2700b08c752d82

PiperOrigin-RevId: 445393094
2 files changed
tree: 6bffeddfae84d480e9d56c7f34a9feae02d491af
  1. quiche/
  2. CONTRIBUTING.md
  3. LICENSE
  4. README.md
README.md

QUICHE

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.