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

Networking discovery and addressing overhaul #48

Open
sneakers-the-rat opened this issue Dec 3, 2020 · 2 comments
Open

Networking discovery and addressing overhaul #48

sneakers-the-rat opened this issue Dec 3, 2020 · 2 comments

Comments

@sneakers-the-rat
Copy link
Contributor

[stubbing out an idea, forgive me while it remains incomplete]

The way networking objects are created and addressed it very clumsy right now.

  • registry for networking objects
  • uniform 'listen' port
  • every node increments ports looking for open ports and stores in centralized registry
  • networking stations ping around the network looking for autopilot objects, and then when they find them exchange a handshake that lists all the networking objects available beneath them
  • as new networking objects are created, let the rest of the swarm know -- do we want a full-knowledge system or like a DHT?

related to another sorta fundamental revision to the notion of id in the system that needs its own architecture issue

@sneakers-the-rat
Copy link
Contributor Author

this looks like essentially exactly what we're looking for: https://rfc.zeromq.org/spec/48/

@sneakers-the-rat
Copy link
Contributor Author

sneakers-the-rat commented May 28, 2021

or no like this https://rfc.zeromq.org/spec/36/

nope yep this will transform the tool^^

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

1 participant