| commit | 96840a0ea972fc4c8d03de24df47e367d60bfcda | [log] [tgz] |
|---|---|---|
| author | martinduke <martinduke@google.com> | Thu Jul 14 07:09:06 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 14 07:10:07 2022 -0700 |
| tree | 790aac6adb4ea3f056d6114ea11fd59574dbb2d5 | |
| parent | 8eb90efcb29c26fd377fee84357adc74e4482ecd [diff] |
Store original server connection IDs in the dispatcher's session map. Release them when the 0-RTT key discard timer fires. Include them in the list of active connection IDs to make sure they are destroyed if the timer never fires. Protected by quic_restart_flag_quic_map_original_connection_ids. PiperOrigin-RevId: 460950140
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.