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 10:28, 29 July 2015
, 10:28, 29 July 2015→Sketch
(→Intro) |
(→Sketch) |
||
| Line 33: | Line 33: | ||
* Those two MAM IDs are not identical. Romeo and Julia store the same message in their MAM Archive under different IDs | * Those two MAM IDs are not identical. Romeo and Julia store the same message in their MAM Archive under different IDs | ||
* All involved clients use MAM to display those parts of the conversation happened while they where offline | * All involved clients use MAM to display those parts of the conversation happened while they where offline | ||
* If a client connects, it requests the MAM archived messages starting from the last | * If a client connects, it requests the MAM archived messages starting from the last message known to be archived, using the Message ID of that message. From a clients perspective, the last message known to e archived is either the last incoming message (with a MAM ID), or the last send message by that client, for which the client calculated the message ID, that got xep198 ack'ed. | ||
== Carbons vs. MR2. vs Goal == | == Carbons vs. MR2. vs Goal == | ||