From 1890662f65b8ebc23c25dbfb9b81e715267a33d9 Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Fri, 16 Jan 2015 16:02:59 +0000 Subject: [PATCH] FetchAll is no longer sent explicitly on ConnectionEstablished though it is in fact still sent straight away as part of initialsing the FetchAll timer --- site/how-it-works.md | 1 - 1 file changed, 1 deletion(-) diff --git a/site/how-it-works.md b/site/how-it-works.md index bbd8224f..08d1c287 100644 --- a/site/how-it-works.md +++ b/site/how-it-works.md @@ -114,7 +114,6 @@ There are two message types: This carries no payload. The receiver responds with the entire topology model as the receiver has it. FetchAll is sent: - * when a new connection is established, by both sides of the new connection * when an update is received that references a peer that the receiver does not know * periodically, on a timer, in case any updates have been missed