[Standards] LAST CALL: XEP-0313 (Message Archive Management)
zash at zash.se
Tue Nov 14 15:38:39 UTC 2017
On Mon, Oct 16, 2017 at 06:38:45PM -0000, Jonas Wielicki wrote:
> This message constitutes notice of a Last Call for comments on
> This document defines a protocol to query and control an archive of
> messages stored on a server.
> This Last Call begins today and shall end at the close of business on
> Please consider the following questions during this Last Call and send
> your feedback to the standards at xmpp.org discussion list:
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
> 2. Does the specification solve the problem stated in the introduction
> and requirements?
- Automatic history synchronization between multiple clients.
I'm not a client developer but it should work for that.
- Calendar-based on-demand display of historic messages in a client
that doesn’t keep local history.
It would be expensive if you want to show which days in the calendar has
messages, but otherwise workable.
- So-called ‘infinite’ scrollback, whereby a client automatically
fetches and displays historical messages naturally in the message
log as the user scrolls back in time.
For the longest time, I believed this part was the primary use case, and
I believe it fulfills this part.
> 3. Do you plan to implement this specification in your code? If not,
> why not?
I have written both server and client library implementations. It may
however not be completely up to date.
> 4. Do you have any security concerns related to this specification?
> 5. Is the specification accurate and clearly written?
It might be more to do with me, but every time I read through it I find
new text that I don't remember seeing before.
I also think that the way preferences are returned seems inconsistent
with the rest of XMPP.
Kim "Zash" Alvefur
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the Standards