You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[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
The text was updated successfully, but these errors were encountered:
[stubbing out an idea, forgive me while it remains incomplete]
The way networking objects are created and addressed it very clumsy right now.
related to another sorta fundamental revision to the notion of
id
in the system that needs its own architecture issueThe text was updated successfully, but these errors were encountered: