Difference between revisions of "Flow/Server based 1-1 chat state"
|Line 11:||Line 11:|
# XMPP-IM (RFC 6121 8.) Message routing is
# XMPP-IM (RFC 6121 8.) Message routing is the goal
# Clients are able to determine the MAM ID before
# Clients are able to determine the MAM ID before send the message
Revision as of 13:19, 4 June 2015
Server based 1-1 chat state
(or: "persistent 1-1 chats involving multiple clients")
- MR2 (or Carbons)
- XMPP-IM (RFC 6121 8.) Message routing is obstructive to achieve the goal
- Clients are able to determine the MAM ID before they send the message
Romeo and Julia want to talk. They both have multiple clients (desktop, mobile device, etc), and they expect that their conversation is completely available on each of their devices.
- If Romeo sends a message to Julia, the message is forked to all other clients of Romeo, and to all clients of Julia
- 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).
- Those two MAM IDs are not identical. Romeo and Julia store the same message in their MAM Archive under different IDs