On Freitag, 22. September 2017 17:48:44 CEST Georg Lukas wrote: > Hi, > > the vast number of different IDs can make a developer dizzy. Can we > please specify in 0359 that an entity adding an <origin-id/> MUST (or at > least SHOULD) set the message-id value of the message to the same ID as > the <origin-id/>? > > It was asked why <origin-id/> would be needed at all then, but when a > client is processing incoming messages, it does help to know if the > sender was generating strong UUIDs
How does that help? > , and the receiver does not always > have access to the sender's entity caps (MUC with MSN, offline > messages). > > This would add a little bit of consistency in a place where we can't go > back in time and fix the original design. I don’t see a reason against that. Keep in mind that @id rewriting MUCs will lead to inconsistency though, so clients MUST be able to deal with that ... . kind regards, Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
