docs(quinn): Clarify effects of setting AckFrequencyConfig #1894
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.
Per discussion in Discord [link], the actual extent to which setting ack_frequency_config to
None
disables the acknowledgement frequency extension is less than the documentation seems to imply. An endpoint with the ack frequency config set toNone
will still:min_ack_delay
field of its transport parameters withSome
The only thing it will not do is send the peer an ACK_FREQUENCY frame.
This PR updates the docs to reflect the behavior more closely.