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

Tracker/proxy versus DHT #2920

Closed
cminnoy opened this issue Jun 29, 2016 · 1 comment
Closed

Tracker/proxy versus DHT #2920

cminnoy opened this issue Jun 29, 2016 · 1 comment

Comments

@cminnoy
Copy link

cminnoy commented Jun 29, 2016

Hi,

I would like to refer to the following comparission (for bittorrent) between DHT and Trackers:
https://www.ietf.org/proceedings/76/slides/ppsp-4.pdf

Would it be usefull for IPFS also to implement a concept of a Tracker?
For example in a LAN, you don't want to have a DHT running around, nor each individual
PC talking direct to the internet.
A Tracker will be faster. I can imagine that corporations will be refusing IPFS on their
network when they can not control/monitor the communication/bandwidth.
A Tracker or Proxy could be helpfull at the edge of the LAN to the WAN.

Cheers,

Chris

@whyrusleeping
Copy link
Member

whyrusleeping commented Jun 29, 2016

ipfs has support for plugable routing mechanisms. It doesnt necessarily need to use the DHT if something else is available. This isnt currently implemented, but can be easily in the future.

If you want to have further discussion towards this, could you please move your issue over to https://github.com/ipfs/notes ? we try to keep issues in this repo down to things directly related to the go implementation of the protocol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants