Networking - LeFreq/Singularity GitHub Wiki

The OS is designed to be maximally generic without sacrificing customizability nor functionality. In the broadest sense, this category is used to convey "communicating between or with other PROCESSING units".

Networking extends the personal computer past it`s physical bounds and virtualizes the entire network, just like the multi-user systems simulated a computer for each user, each peer gets to see the entire network as part of it`s system.

With a peer-to-peer model of say, 6 peers, you have complete connectivity to a 1,000,000+ nodes with roughly 7 hops, but only have to track 6 slots as peers. XXX Four peers will get you on the network, while 8 is ideal.

Nodes without their 4 peers can broadcast their available slot and wait for a new node to come by to create a community of co-sharing partners. To show that you're part of the TEAM.

Data trying to reach a node has to keep track of which nodes it has visited and the OS makes sure that they don't go back to any such previous system.

A NODE can limit the transferrence of packets based on message size, say a fraction of how much memory the NODE has. Larger messages can be harder to send than smaller messages to ensure network sensitivity and build community based on efficient, terse messaging.

Update: if the device isn't mobile, 4 consistent nodes will do. For mobile devices, one can work with 8 peers and still complete the whole.