logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-07 16:43:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: more rephrasing

Browse Source
This commit is contained in:
kaichaosun 2024-07-05 12:09:54 +08:00
parent 8f7fb86f38
commit 5f0d5f8d2e
No known key found for this signature in database
GPG Key ID: 223E0F992F4F03BF
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
standards/application/relay-reliability.md
View File

@ -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: For incoming messages, the processing flow can be like this:
- subscribe to the interested pubsub and content topics - 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. - 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 - batch fetch the full messages corresponding to the missing message hashes in the buffer from the store node
- process the messages - process the messages
- update the last fetch time for the interested topic
The implementation in Python may look like this: The implementation in Python may look like this: