Added more to network model info.
This commit is contained in:
parent
3f4eca40f7
commit
97422a068d
@ -6,7 +6,9 @@ This repository provides a library with interfaces by which you can access the n
|
||||
|
||||
Network Model
|
||||
-------------
|
||||
This model moves further from the federated decentralization model, taking one closer to that of torrents with their peer discovery. There are three components to the network: nodes and directory nodes. All connected machines work as nodes, but only those that are not firewalled can function as directory nodes (nodes that other nodes can connect to). With this model the directory nodes would serve the functionality of trackers in a torrent system (those nodes that have enough uptime to be considered _directory servers_).
|
||||
This model moves further from the federated decentralization model, taking one closer to that of torrents with their peer discovery. There are three components to the network: nodes and directory nodes. All connected machines work as nodes, but only those that are not firewalled can function as directory nodes (nodes that other nodes can connect to). With this model the directory nodes would serve the functionality of trackers in a torrent system (those nodes that have enough uptime to be considered _directory servers_). At first the network will be very much centralized around a single _directory server_, however when new _directory servers_ start popping up (any directory node with long uptimes) it will help to further remove dependence on a single point of vulnerability and help towards the decentralization of the network. Clients will remember what nodes they connected to so that upon startup they can try other directory nodes and not simply the same one, allowing for the network to quickly move forward from the original _directory server_.
|
||||
|
||||
For more information on the network model, please refer to the wiki.
|
||||
|
||||
API Documentation
|
||||
-----------------
|
||||
|
Loading…
Reference in New Issue
Block a user