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

docs: clarify that losses are possible message losses

Browse Source
This commit is contained in:
Hanno Cornelius 2025-03-26 12:34:07 +00:00
parent acdc89d0e8
commit 9d8c7b84d4
No known key found for this signature in database
GPG Key ID: 081F615B3EDEF8DE
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
standards/application/p2p-reliability.md
View File

@ -237,7 +237,7 @@ The interval between each retransmission attempt is up to the implementation,
but we RECOMMEND starting with `1 second` and increasing it after each failure.
- The client MAY consider a message publication as having failed irremediably after a set number of failed lightpush requests.
#### 4. Retransmit on loss detection
#### 4. Retransmit on possible message loss detection
> *_Note:_* Lightpush clients participating in [Store-based reliability](#store-based-reliability) already performs this strategy and can ignore this section.
@ -293,7 +293,7 @@ or after a single `SUBSCRIBE` failure.
by submitting the same filter criteria as before in a new [`SUBSCRIBE`](https://github.com/vacp2p/rfc-index/blob/7b443c1aab627894e3f22f5adfbb93f4c4eac4f6/waku/standards/core/12/filter.md#subscribe) request to the same service node.
This helps ensure that local and remote views of filter criteria remains synchronised.
#### 4. Store query on loss detection
#### 4. Store query on possible message loss detection
> *_Note:_* Filter clients participating in [Store-based reliability](#store-based-reliability) already performs this strategy and can ignore this section.