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

Service Discovery #64

Closed
metasean opened this issue Jun 12, 2015 · 4 comments
Closed

Service Discovery #64

metasean opened this issue Jun 12, 2015 · 4 comments
Labels

Comments

@metasean
Copy link
Collaborator

Currently peers must be hard-coded into an application. Service Discovery will allow peers to let one another know what other peers are potentially available.

@metasean metasean added the new label Jun 12, 2015
@Xe
Copy link

Xe commented Jun 12, 2015

consul exists. Don't reinvent the wheel.

@r14c
Copy link

r14c commented May 12, 2016

I've been thinking about implementing something like this using the DHT to allow peers to announce their participation in a given data mesh. feross/torrent-discovery could cover that use-case pretty easily once Gun has WebRTC support.

The main concerns I have are name collisions and data security. A private DHT or tracker setup could mitigate both of these, but it would be nice to be able to safely use the mainline DHT.

@amark
Copy link
Owner

amark commented May 13, 2016

You'll have to talk more about this at the meet up. I don't have much experience in this area.

@amark
Copy link
Owner

amark commented Feb 20, 2017

WebRTC still unfortunately is very difficult to work with (I had simple-peer working with people geographically nearby but not across large distances).

Anyways, service discovery should be a layer on top of gun, like a driver/adapter, not gun core itself. So I'm gonna label this as a feature request (although will be pretty important) and ask to have it put in: https://github.com/gundb/feature-requests and close it here (since it isn't a bug in core). Thanks!

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

No branches or pull requests

4 participants