mirror of
https://code.briarproject.org/briar/briar.git
synced 2026-02-14 19:59:05 +01:00
Update messages removable media mailbox
@@ -13,19 +13,58 @@ Then we have the following scenarios -
|
||||
| is online | msg type | has MB | MB online | exports msg | before/after MB upload | receives acks | ack medium |
|
||||
| ------ | ------ | ------ | ------ | ------ | ------ | ------ | ------ |
|
||||
| yes | text | yes | yes | yes | after | yes | MB |
|
||||
| yes | photo | yes | no | yes | before| | |
|
||||
| yes | photo | yes | yes | yes | after | yes | Rem Media |
|
||||
| cell | cell | cell | cell | cell | cell | | |
|
||||
| cell | cell | cell | cell | cell | cell | | |
|
||||
|
||||
**Recipient**
|
||||
|
||||
| is online | msg type | has MB | MB online | exports msg | before/afterMB upload |
|
||||
| is online | msg type | has MB | MB online | exports ack | before/afterMB upload |
|
||||
| ------ | ------ | ------ | ------ | ------ | ------ |
|
||||
|yes | cell | cell | cell | cell | cell |
|
||||
| cell | cell | cell | cell | cell | cell |
|
||||
|no | text | yes | yes | yes | na |
|
||||
| no | photo | yes | yes | yes | after |
|
||||
| cell | cell | cell | cell | cell | cell |
|
||||
| cell | cell | cell | cell | cell | cell |
|
||||
|
||||
**Scenario 1**
|
||||
Recipient receives message from the removable media, but sends ack via mailbox
|
||||
In this scenarios, a text message is created by the sender, and they have a MB which is available online. So the message they created is uploaded to their mailbox.
|
||||
- The message is not downloaded - let's say that the intended recipient is offline and cannot download the message
|
||||
- The sender can export the same message onto the removable media.
|
||||
- The sender goes offline after this
|
||||
- The recipient can upload the message from the removable media.
|
||||
- The recipient comes back online
|
||||
- The recipient's mailbox is online, which means that the ack their Briar app generates will be uploaded onto their MB
|
||||
- Sender comes back online and received the ack from the recipient's mailbox
|
||||
- The message that the sender sent to the recipient now has 2 ticks
|
||||
|
||||
**Scenario 2**
|
||||
|
||||
**Sender**
|
||||
| is online | msg type | has MB | MB online | exports msg | before/after MB upload | receives acks | ack medium |
|
||||
| ------ | ------ | ------ | ------ | ------ | ------ | ------ | ------ |
|
||||
| yes | photo | yes | yes | yes | after | yes | Rem Media |
|
||||
|
||||
**Recipient**
|
||||
|
||||
| is online | msg type | has MB | MB online | exports ack | before/afterMB upload |
|
||||
| ------ | ------ | ------ | ------ | ------ | ------ |
|
||||
| no | photo | yes | yes | yes | after |
|
||||
|
||||
|
||||
Recipient receives message from sender's mailbox and sends ack via removable media
|
||||
- a photo message is created by the sender, and this message is uploaded to their mailbox as the intended recipient is offline.
|
||||
- Sender goes offline
|
||||
- Recipient comes online, and receives a message from the sender's mailbox
|
||||
- Thier own ack is generated automatically and ploaded to their own mailbox, as the sender is now offline.
|
||||
- The recipient exports the ack to removable media
|
||||
- The sender imports the ack from the removable media and the message gets the second tick
|
||||
- The sender comes back online
|
||||
- at this point the ack sent to them by the recipient's mailbox should be downloadd and deleted - but for the user this is transparent - they don't see any changes on their screen while this is being done.
|
||||
- Now both recipient and the sender of the original message are online and they message each other directly, without messages passing through MB
|
||||
|
||||
**Scenarios 3**
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user