From e549e966579cdacd49cd10b945a59ce2163b97e3 Mon Sep 17 00:00:00 2001 From: Zlatin Balevsky Date: Tue, 10 Jul 2018 05:14:36 +0100 Subject: [PATCH] uuid in crawler pings and pongs --- doc/crawler.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/doc/crawler.md b/doc/crawler.md index 0adab8bc..e637c261 100644 --- a/doc/crawler.md +++ b/doc/crawler.md @@ -4,23 +4,25 @@ Crawling the network is one possible method for a HostCache to discover currentl ### Crawler Ping -The crawler ping is a message sent in a signed datagram to the target ultrapeer. It contains uncompressed JSON payload with just the message type and version: +The crawler ping is a message sent in a signed datagram to the target ultrapeer. It contains uncompressed JSON payload with the message type, version and an UUID: ``` { type: "CrawlerPing", - version: 1 + version: 1, + uuid: "asdf-1234-..." } ``` ### Crawler Pong -The ultrapeer responds with the following message, also in a signed datagram. It contains the list of Destinations that it is currently connected to. Since the datagram is limited in size, not all Destinations will be able to fit in it, but that should be fine for the purpose of ultrapeer discovery. +The ultrapeer responds with the following message, also in a signed datagram. It contains the list of Destinations that it is currently connected to. Since the datagram is limited in size, not all Destinations will be able to fit in it, but that should be fine for the purpose of ultrapeer discovery. The "uuid" field must match that of the CrawlerPing. ``` { type: "CrawlerPong", version: 1, + uuid: "asdf-1234-...", clientVersion: "MuWire 1.2.3", peers: [ b64.1, b64.2...] }