[jdev] Offline messages XEPs interoperability (XEPs 0013 and XEP-0160)

Sergey Dobrov binary at jrudevels.org
Fri Feb 21 18:00:07 UTC 2014

Oh, such a nice discussion have started suddenly, thanks :)

Thanks Matthias for such a detailed response, it's very nice.

I would agree that XEP-0013 is good to deprecate now, but I'd move this 
to MAM instead. I do remember the cases when clients got really flooded 
with offline messages. Also, it might be a good idea for mobile clients 
to show number of offline messages for each contact but fetch them only 
when user activates appropriate contact in roster. I think this is the 
best case that explains the necessity of such a protocol. (but again, 
XEP-0013 is really obsolete)

Also, from the contacts with multiple resources: it might be nice to 
have a possibility for different resources to have "unread" messages 

1) user logs in from 1st client
2) it retrieves some offline messages from some contacts but not all
3) he decides to move to the mobile
4) he can still see which messages are remaining not read through MAM

I would really love such a feature, do you?

On 21/02/2014 19:49, Christian Schudt wrote:
>> Well, feedback would be good. My impression is that people haven't implemented and deployed XEP-0013 very much. If that's false or if you find it useful, please speak up. :-)
> Personally I don't find XEP-0013 very useful and others probably, too, which might be a reason, that it's not widely implemented.
>  From an end user's perspective (client) I wouldn't want to first retrieve the number of offline messages, then the headers and then retrieve single messages and maybe even delete some of them (purge).
> I'd rather just want to retrieve all full offline messages directly, in the same way as I would retrieve them while being online.
> But maybe others have some good use cases for it.
> _______________________________________________
> JDev mailing list
> Info: http://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: JDev-unsubscribe at jabber.org
> _______________________________________________

More information about the JDev mailing list