165
edits
Difference between revisions of "Flow/Server based 1-1 chat state"
Jump to navigation
Jump to search
Flow/Server based 1-1 chat state (view source)
Revision as of 08:35, 12 August 2015
, 08:35, 12 August 2015→Sketch
(→Intro) |
(→Sketch) |
||
| Line 32: | Line 32: | ||
* When the message arrives at Julia clients, it will contain the MAM ID under which it was stored in Julia's MAM Archive | * When the message arrives at Julia clients, it will contain the MAM ID under which it was stored in Julia's MAM Archive | ||
* Romeo is able to calculate the MAM ID under which the message was stored in his MAM Archive, by concatenating the Message ID with the Stream ID (or another suitable ID told to Romeo's client). | * Romeo is able to calculate the MAM ID under which the message was stored in his MAM Archive, by concatenating the Message ID with the Stream ID (or another suitable ID told to Romeo's client). | ||
* A Stream Management ack | * A Stream Management ack should probably mean that ack'ed messages have been added to the users MAM archive | ||
** It's currently undefined what should happen if the message could not be added (e.g. because the archive storage's space is full) | ** It's currently undefined what should happen if the message could not be added (e.g. because the archive storage's space is full) | ||
** I'd expect impls to somehow indicate the MAM error but continue to process the message. That is route and SM ack it. | ** I'd expect impls to somehow indicate the MAM error but continue to process the message. That is route and SM ack it. | ||