From ef8a4823b02f348cfe6bdac365e686125113be7b Mon Sep 17 00:00:00 2001 From: kaichao Date: Fri, 5 Jul 2024 11:42:56 +0800 Subject: [PATCH] Update standards/application/relay-reliability.md Co-authored-by: Hanno Cornelius <68783915+jm-clius@users.noreply.github.com> --- standards/application/relay-reliability.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standards/application/relay-reliability.md b/standards/application/relay-reliability.md index 686e3ff..1107a9b 100644 --- a/standards/application/relay-reliability.md +++ b/standards/application/relay-reliability.md @@ -105,7 +105,7 @@ An application could use different pubsub topics and content topics, for example For incoming messages, the processing flow can be like this: - subscribe to the interested pubsub and content topics - query the store node with the interested topics and time range for message hashes periodically -- check if the message hash is exist in local database, if not, adding the message hash to a buffer, if yes, skip the message +- check if each received message hash already exists in the local database. if not, add the missing message hash to a buffer. - batch fetch the full messages corresponding to the missing message hashes in the buffer from the store node - process the messages necessarily - update the last fetch time for the interested topic