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.

Sign up for GitHub

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

Jump to bottom

Add events indicating reasons for stalls #90

Closed

rmarx opened this issue May 26, 2020 · 1 comment

Labels

future-versions

Contributor

rmarx commented May 26, 2020 •

edited

Loading

For example, an application might have more data ready to send, but cannot due to Flow Control or Congestion Control or Anti-Amplification limits.

These are currently only observable for the Flow Control case and only if the sender sends *_BLOCKED frames (which is optional).

I'm not sure in which category this type of event would belong though... maybe look at msquic's handling (they have this type of event for sure).

rmarx added the future-versions label

Contributor Author

rmarx commented Aug 18, 2021

Duplicate of more detailed #132

rmarx closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment