-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
consul exists. Don't reinvent the wheel. |
I've been thinking about implementing something like this using the DHT to allow peers to announce their participation in a given data mesh. 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. |
You'll have to talk more about this at the meet up. I don't have much experience in this area. |
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! |
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.
The text was updated successfully, but these errors were encountered: