| commit | 53cbf3f57e5c4e652567df43bedb2631d012eee8 | [log] [tgz] |
|---|---|---|
| author | haoyuewang <haoyuewang@google.com> | Tue Apr 13 12:52:11 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 13 12:52:42 2021 -0700 |
| tree | eec81c356e1db5cd587b78c8475555e54211860f | |
| parent | 1ad3f0669eada80f7a2f2c72249c0bb570575f8e [diff] |
Group sending path response and reverse path challenge closer on the server side. The advantages are: (1) The outermost ScopedPeerAddressContext can be instantiated after alternative_path_ has been created. This makes it straightforward to find a connection ID for this scoped context. (2) Ideally, path response and reverse path challenge is better sent at the end of packet processing. But that is a more complex change. The current change allows progress made in usage of connection ID without that. Protected by FLAGS_quic_reloadable_flag_quic_group_path_response_and_challenge_sending_closer. PiperOrigin-RevId: 368275656 Change-Id: I1735ff20babd2f190ba27ea7037e2be9317a6f3a
QUICHE (QUIC, Http/2, Etc) is Google‘s implementation of QUIC and related protocols. It powers Chromium as well as Google’s QUIC servers and some other projects. QUICHE is only supported on little-endian platforms.
Code can be viewed in CodeSearch in Quiche and is imported into Chromium.