logos-messaging/pm
1
0
Fork 0
mirror of https://github.com/logos-messaging/pm.git synced 2026-01-03 22:53:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: update SDS FURPS

Browse Source
This commit is contained in:
Hanno Cornelius 2025-05-27 13:18:54 +01:00 committed by fryorcraken
parent b764657f21
commit 3f84a5fa5a
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
1 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
FURPS/application/sds.md
View File

@ -3,12 +3,15 @@
## Functionality ## Functionality
1. Ability to know that a published message has been received by at least one member of the group (and could therefore eventually be retrieved by other members). 1. Ability to know that a published message has been received by at least one member of the group (and could therefore eventually be retrieved by other members).
2. Ability for participants to know when they have missed a message, and to retrieve them using Waku store protocol 2. Ability for participants to know when they have missed a message
3. Ability to resend unacknowledged messages
4. Ability to retrieve missed messages using Waku store protocol
## Usability ## Usability
1. When sending a message to a large group, the application knows whether it was received by other group members, with high probability 1. When sending a message to a large group, the application knows whether it was received by other group members, with high probability
2. When being part of a large group, the application is able to know whether they are missing messages, and is able to retrieve missed messages 2. When being part of a large group, the application is able to know whether they are missing messages
3. When being part of a large group, the application is able to retrieve missed messages
## Reliability ## Reliability
@ -19,9 +22,10 @@
Assuming messages in a group are sent at least every `S` seconds. Assuming messages in a group are sent at least every `S` seconds.
1. When sending a message in a group, the publisher can ensure the message was received by at least one recipient within`S` seconds **(Vac-DST)** 1. When sending a message in a group, the publisher can ensure the message was received by at least one recipient within `S` seconds **(Vac-DST)**
2. When receiving messages in a group, the receiver can detect 90% of missed messages within `3*S` seconds, and reach eventual consistency within `6*S` seconds **(Vac-DST)** 2. When receiving messages in a group, the receiver can detect 90% of missed messages within `3*S` seconds
3. When receiving messages in group, the receiver can reach eventual consistency within `6*S` seconds **(Vac-DST)**
## Supportability ## Supportability
1. Applied to Communities channels only, both Status Mobile and Desktop 1. Applied to Communities channels on Status Desktop