| commit | 4ab6cb703f49ca9a3dd72a628121219e75213ab9 | [log] [tgz] |
|---|---|---|
| author | martinduke <martinduke@google.com> | Thu Apr 03 09:23:29 2025 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 03 09:24:52 2025 -0700 |
| tree | 11b53912646b4fc05e5d628ace28d91927dda4f9 | |
| parent | f25dd3c576c4986e5b7334a5b783132f231b8bb2 [diff] |
Increase array size in QuicConnectionId. Some users of this class try to minimize heap allocations, and compliant QUIC clients can pick IDs that trigger a heap allocation. Also, when we eventually transition to encrypted connection IDs, CID length close to the maximum will become the norm. This increases the size of QuicConnectionId from 16B to 24B, undoing the performance gain from cl/338718268 for the (current) common case where connection IDs are 8B. PiperOrigin-RevId: 743590623
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.