reweave/weave
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor: rename PeerCache to Peers

Browse Source 
It was never much of a cache, and that aspect of it is certainly not
its defining characteristic.
This commit is contained in:
Matthias Radestock committed 2014-12-24 19:23:43 +00:00
1 parent e8f836ad85
commit 2b2f47c031
4 files changed
+66 -67
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/architecture.txt
+12 -13
View File
@@ -96,19 +96,18 @@ Router:
directly connected neighbours via TCP. This network update message
contains the relevant changes to the network topology due to the
connection change. When such a message is received by a TCP
receiver threads, they invoke the peers cache to apply the update
to the local model of the network topology. This may fail for a
number of reasons (for example the update may contain reference to
peers that we have no prior knowledge of. In this case, we ignore
the update and send back to the peer from whom we received the
update a request for the complete network topology), or it may
apply and elicit some changes to our model. If it does elicit some
changes then we send out an updated update message to all our
peers. In this way the changes are passed quickly from peer to
peer based on the established connections and stop being sent once
a received update causes no changes to the peer's topology
model. Changes are additive and care is taken to ensure that no
loops can occur.
receiver threads, they apply the update to the local model of the
network topology. This may fail for a number of reasons (for
example the update may contain reference to peers that we have no
prior knowledge of. In this case, we ignore the update and send
back to the peer from whom we received the update a request for
the complete network topology), or it may apply and elicit some
changes to our model. If it does elicit some changes then we send
out an updated update message to all our peers. In this way the
changes are passed quickly from peer to peer based on the
established connections and stop being sent once a received update
causes no changes to the peer's topology model. Changes are
additive and care is taken to ensure that no loops can occur.
Routing