[Standards] "Chronological" order in XEP-0313 (Message Archive Management)

Kevin Smith kevin.smith at isode.com
Thu May 19 09:09:06 UTC 2016


On 19 May 2016, at 09:21, Georg Lukas <georg at op-co.de> wrote:
> we just had a discussion in the prosody MUC, regarding message ordering
> in MAM, and I realized there is some ambiguity in the XEP when handling
> incoming <delay> elements.
> 
> The XEP explicitly states that messages must be sorted chronologically:
...
> However, it does not make clear how to handle messages that already
> contain a <delay> element (i.e. because the client was disconnected when
> the user entered the message).

MAM stamps the <delay/> inside the <forwarded/>, so I don’t see this is an issue.

> These are all not shiny, but one way or the other, there should be some
> clarification in the XEP regarding what "chronological" actually means
> and how incoming <delay> elements should be processed.

The intention is the time that it is received by the archiving entity. Not to be doing DPI and reordering based on time information from externally-generated metadata.

/K


More information about the Standards mailing list