[Standards] Dealing with offline messages in times of MAM

Dave Cridland dave at cridland.net
Wed Jun 10 08:56:15 UTC 2015

On 10 June 2015 at 05:58, Daniel Gultsch <daniel at gultsch.de> wrote:

> Even though not yet quite perfect (see the discussion about Message-ID and
> MR2) MAM works reasonable well. A MAM capable client has no trouble to
> automatically catch up with lost messages.  However if the MAM capable
> client is the only client in the game it will (with normal setups)
> regularly receive both the offline messages and the messages downloaded
> from the MAM archive. Now client side de-duplication usually works good
> enough for the average user not to notice however this is far from being an
> ideal solution.
> Is there a solution to this problem that can simply be solved by server
> side configuration?
> Will simply disabling offline message return all messages to the sender
> even though they are stored in MAM?
> Maybe it is time to develop some business rules or best practises that
> deal with this scenario and the maybe similar scenario of what should
> happen with messages that get failed due to a SM time out.
SM is easy - discard all <presence/>, bounce all <iq/> set/get, and
redeliver all <message/>. (Technically, you can bounce a <presence
type='probe'/> too).

For offline messages and MAM-capable clients, there's always XEP-0013,
though that's rather more heavyweight than we need.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20150610/afc4ed8f/attachment.html>

More information about the Standards mailing list