On 23.09.2017 10:13, Jonas Wielicki wrote: > 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 ... .
I think I don't understand the benefits from Georg's suggestion, so currently one reason against is that it adds more complexity without any gain from my PoV. Plus what you said: The scheme will break as soon as the MUC service, or any other service doing some sort of reflection, rewrites the 'id' attribute of the stanza (which MUC services are allowed to, and are the reason for xep359 existence in the first place). - Florian
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
