Difference between revisions of "Flow/Server based 1-1 chat state"

Jump to navigation Jump to search
 
Line 36: Line 36:
** 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.
* Those MAM IDs of different entities are not identical. Romeo and Julia store the same message in their MAM Archive under different IDs
* Those MAM IDs of different entities 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 fetch (and 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 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.
* 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.


163

edits

Navigation menu