Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prevent hot loop when 0rtt is rejected #587

Merged
merged 1 commit into from
Jul 29, 2024
Merged

Conversation

kazuho
Copy link
Member

@kazuho kazuho commented Jul 29, 2024

At the moment, scheduler_can_send returns 1 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 of quicly_send at an earliest moment. Each time quicly_send is called, zero packets will be emitted, but quicly_get_first_timeout will continue requesting immediate invocation.

@kazuho kazuho merged commit 07c15d0 into master Jul 29, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant