> * Old participants never die, they're merely removed from the pubsub > node and require endless searching through MAM, or having all their data > copied to the outgoing messages. [..] I don't understand what this is about. Can you expand? Given a message, (some/many/rare) clients need to know who actually sent the message. This means knowing detailed information about the sender - we can do this in (roughly) three ways: * Include the key information in the message itself. This is roughly what we're doing in the <mix/> element currently. * Include pointers to the information. MUC does this pattern, but it suffers where the pointer expires (points to someone who is no longer an occupant/participant) * Include pointers to the information and expect client to locate that information in the *archive* of the participants node. MIX started off on the third option and has moved to the first, generally. [Steve Kille] My intent is that there should be enough in the message so that in a typical use case, the receiver can display what is needed without needing to do any fancy lookup. There are still special cases where the client may want to find more stuff Steve
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
