2017-09-22 17:48 GMT+02:00 Georg Lukas <[email protected]>: > 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/>?
yes. I think most implementations will naturally do this anyway because reusing the stanza id is 'easier' than coming up with a new one. And you only have to keep track of one ID in your database. To be fair having the wording in the XEP doesn't really change much because the rules of giving origin-id precedence over stanza-id when it comes to deduplication; references or whatnot obliges to the receiving end. (Or the XEPs in question) However actually defining something as SHOULD what most client developers will do anyway because it's the only sane way to do it will make the use case of origin-ids a bit more obvious to newcomers and Georg feel less dizzy. cheers Daniel _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
