Quoting Peter Saint-Andre <[EMAIL PROTECTED]>:
If clients recognize the message IDs, they could also include an
In-Reply-To SHIM header as described in JEP-0131 and include the
message ID there.
Here's the problem though. Presumably the MUC service, operating as a
component, has to assign new and unique message IDs to every message. That
means that if both you and I are in the same conference room, the same message
will have one ID when received by me, and one ID when received by you.
For this to work in a practical situation, the conference server would have to
track all the IDs given out. For a room with 100 participants, this means
remembering 100 message IDs per message.
And naturally, you can't just send the 100 stanzas out with the same
ID, because
if you got an error back, you'd ideally want to map it to the correct
stanza you
sent.
TX
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
