Allow UDP clients to limit peers in response #1035
Merged
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.
The UDP tracker announce response always include all peers available up to a maxium of 74 peers, ignoring the
num_want
param in the request described in:https://www.bittorrent.org/beps/bep_0015.html
This change applies that limit only when is lower than then TORRENT_PEERS_LIMIT (74).
It also adds the
numwant
GET param to the announce request for the HTTP tracker for the same purpose.num_want
, positional param in the UDP packet).numwant
GET param).