Skip to content
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.

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

[Feature Request] BitTorrent vs HTTP optimization #2

Closed
gatesyp opened this issue Feb 14, 2017 · 2 comments
Closed

[Feature Request] BitTorrent vs HTTP optimization #2

gatesyp opened this issue Feb 14, 2017 · 2 comments

Comments

@gatesyp
Copy link
Member

gatesyp commented Feb 14, 2017

Find the point where BitTorrent outperforms using http method.

Then, automatically switch to using BitTorrent protocol in order to maintain extremely high download speeds

@csinko
Copy link
Contributor

csinko commented Mar 13, 2017

Upon further thinking, implementing a BitTorrent protocol has a lot of advantages. The main one being if a node becomes slow, crashes, or becomes disconnected from the network, downloading can automatically transfer to another node without interruption.

In addition, in situations where only WiFi can be used to host nodes, BitTorrent could realistically yield better download speeds.

While the speed differences may be negligible in other cases, I do not see any cons to moving towards a Bit / Web Torrent Method, but hash checking and more dynamic software file management should be implemented first before doing so.

@csinko
Copy link
Contributor

csinko commented May 29, 2017

Closing due to duplicate with issue #26. If you would like to follow progress, please refer to #26.

@csinko csinko closed this as completed May 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants