| commit | acfdb39e6b7b4af003c245bb741630063930be9c | [log] [tgz] |
|---|---|---|
| author | martinduke <martinduke@google.com> | Tue May 23 15:23:55 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue May 23 15:25:50 2023 -0700 |
| tree | 315eeaecf5be814eaa8c793a1ac33865e20d7f16 | |
| parent | 7fb9bc3585637f1f29cb25de84f10548f37e223a [diff] |
Refactor PerPacketOptions for QuicWriter. From the bug: per_packet_options_ was originally designed as a vehicle for platforms to get specific instructions to their corresponding QuicWriters via a QuicConnection that didn't understand the semantics of those instructions. Therefore, it is passed to QuicConnection as a piece of memory of which the platform retains ownership. Over time, other instructions specific to QuicConnection have appeared in this struct, as it provides a vehicle to send information to QuicWriter without changing APIs. But this violates the intent of the struct, makes Quiche functions reliant on a piece of memory owned by the platform, and is bug prone (e.g., if the platform provides the same piece of memory for all connections in a dispatcher, the outcome will be very bad). PiperOrigin-RevId: 534577370
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.