From 1dde9bfe0b704c066a1696f5f7f5a0c261b7c85a Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Fri, 23 Jan 2015 16:58:59 +0000 Subject: [PATCH] cosmetic --- site/how-it-works.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/site/how-it-works.md b/site/how-it-works.md index 0c119be4..c5202e51 100644 --- a/site/how-it-works.md +++ b/site/how-it-works.md @@ -107,8 +107,8 @@ MAC discovery. ### Topology Communication -Topology is communicated over the TCP links between peers. -There are two message types: +Topology is communicated over the TCP links between peers. There are +two message types: ##### FetchAll This carries no payload. The receiver responds with the entire @@ -126,23 +126,23 @@ that have just connected * when a connection is deleted - the update contains just the peer that lost the connection -The receiver merges it with its own topology model. If the payload is a -subset of the receiver's topology, no further action is +The receiver merges it with its own topology model. If the payload is +a subset of the receiver's topology, no further action is taken. Otherwise, the receiver sends out to all its connections an "improved" update: - - elements which the original payload added to the - receiver are included - - elements which the original payload updated in the - receiver are included - - elements which are equal between the receiver and - the payload are not included - - elements where the payload was older than the - receiver's version are updated + - elements which the original payload added to the receiver are + included + - elements which the original payload updated in the receiver are + included + - elements which are equal between the receiver and the payload are + not included + - elements where the payload was older than the receiver's version + are updated -If the update mentions a peer that the receiver does not know, -then the entire update is rejected and the receiver sends a -FetchAll message back to the sender. +If the update mentions a peer that the receiver does not know, then +the entire update is rejected and the receiver sends a FetchAll +message back to the sender. #### Message details A topology update message is laid out like this: