prevent hot loop when 0rtt is rejected #587
Merged
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
At the moment,
scheduler_can_send
returns1
if 0-RTT is rejected and there is some application data to be sent.This results in a hot loop in the applications, as
quicly_get_first_timeout
would request invocation ofquicly_send
at an earliest moment. Each timequicly_send
is called, zero packets will be emitted, butquicly_get_first_timeout
will continue requesting immediate invocation.