From 5f0d5f8d2e7f229420787af91505f8d9b9e687b3 Mon Sep 17 00:00:00 2001 From: kaichaosun Date: Fri, 5 Jul 2024 12:09:54 +0800 Subject: [PATCH] chore: more rephrasing --- standards/application/relay-reliability.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/standards/application/relay-reliability.md b/standards/application/relay-reliability.md index d66a665..f5aedb6 100644 --- a/standards/application/relay-reliability.md +++ b/standards/application/relay-reliability.md @@ -106,11 +106,10 @@ 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 +- periodically query the store node with the interested topics and time range for message hashes - 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 -- update the last fetch time for the interested topic The implementation in Python may look like this: