feat: add reqq field support #2246
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DiegoRBaquero
approved these changes
Jan 17, 2022
|
I rebased on current master. Is it expected that node 16 tests are stuck? |
webtorrent-bot
pushed a commit
that referenced
this pull request
Jan 20, 2022
# [1.7.0](v1.6.0...v1.7.0) (2022-01-20) ### Features * add reqq field support ([#2246](#2246)) ([8de2a13](8de2a13))
|
🎉 This PR is included in version 1.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
@DiegoRBaquero Thank you! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[ ] Bug fix
[X] New feature
[ ] Other, please explain:
What changes did you make? (Give an overview)
This PR adds support for the
reqqfield in the enhanced header, as described in BEP 10. Thereqqfield allows a client to specify the maximum number of outstanding requests it supports.Which issue (if any) does this pull request address?
It implements the last part of #1995.
Is there anything you'd like reviewers to focus on?
Honoring the field properly requires to change the logic in
_updateWire()to makemaxOutstandingRequestsa hard limit.