From e756a44a51df3df9ee69e4535cd4a28b670de16e Mon Sep 17 00:00:00 2001 From: Cristian Maglie Date: Wed, 26 May 2021 14:59:43 +0200 Subject: [PATCH] Added more details about message sequencing --- RFCs/0002-pluggable-discovery.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/RFCs/0002-pluggable-discovery.md b/RFCs/0002-pluggable-discovery.md index 225a087..4646b26 100644 --- a/RFCs/0002-pluggable-discovery.md +++ b/RFCs/0002-pluggable-discovery.md @@ -48,7 +48,7 @@ All the commands listed in this specification must be implemented in the discove After startup, the tool will just stay idle waiting for commands. The available commands are: `HELLO`, `START`, `STOP`, `QUIT`, `LIST` and `START_SYNC`. -The discovery must not introduce any delay in the protocol and must respond to all commands as fast as possible. +After each command the client always expect a response from the discovery. The discovery must not introduce any delay and must respond to all commands as fast as possible. #### HELLO command @@ -242,6 +242,8 @@ After this message the discoery will send `add` and `remove` event asyncronoushl The `error` field must be set to `true` and the `message` field should contain a description of the error. +Once in "event" mode, the discovery is allowed to send `add` and `remove` messages asynchronously in realtime, this means that the client must be able to handle these incoming messages at any moment. + The `add` event looks like the following: ```JSON