| commit | 1622578fae2d1c43456b6bb21fe73bbeea8f0547 | [log] [tgz] |
|---|---|---|
| author | danzh <danzh@google.com> | Wed Oct 01 15:35:48 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 01 15:36:46 2025 -0700 |
| tree | 20ee65520f5ab42ef907da32372d1d137ac6cb96 | |
| parent | 368925bfb4b47f0d45c8c614a9b66cda91f114b4 [diff] |
A few changes to connection migration code which is not being used: Change QuicForceBlockablePacketWriter from a pure virtual interface to an implementation of QuicPacketWriterWrapper to avoid diamond inheritance in existing test packet writers which are already inheriting from QuicPacketWriterWrapper and will be used by QuicSpdyClientSessionMigration in tests in the future. Implement TimeSinceLastStreamClose() instead of leaving it as a pure virtual interface. Change QuicSpdyClientSessionWithMigration::OnServerPreferredAddressAvailable() also calls into base class OnServerPreferredAddressAvailable() PiperOrigin-RevId: 813943031
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.