You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebSeeding support is not only about the specific technology. It's also integrating a webseed-aware piece selection algorithm, because HTTP servers prefer one big data chunk request that lot of small ones like in torrents.
More specifically, this would mean having an algorithm that try to create large gaps in pieces selection that can be filled by one single HTTP request.
Considering this and the fact that webseeds are not so common (at least in my use-cases), I would say other features like rarest-first piece selection algorithm, code refactoring / modularisation and why not uTP and PEX would be more useful features for now, leading to direct performance enhancement in most cases.
See also webtorrent/webtorrent#67 for a thorough breakdown of web seeding and to hopefully not duplicate work on this.
Note that a webseed-aware piece selection algorithm is not necessary, but rather a nice-to-have. You could implement web seed peers and no special piece selection handling as a first pass and then implement the special-cased piece selection logic secondly; the existing piece reservation mechanic should work well for this purpose.
we should support web seed, http://en.wikipedia.org/wiki/BitTorrent#Web_seeding
The text was updated successfully, but these errors were encountered: