[Standards-JIG] UPDATED: JEP-0136 (Message Archiving)

Olivier Goffart ogoffart at gmail.com
Wed May 3 23:14:31 UTC 2006


Le Mercredi 3 Mai 2006 18:53, JEP Editor a écrit :
> Version 0.5 of JEP-0136 (Message Archiving) has been released.
>
> Abstract: This document defines mechanisms for server-side archiving of
> XMPP messages.
>
> Changelog: Integrated text from server-side archiving proposal; added
> partial support to collection retrieval; harmonized XML formats and
> namespaces; defined Jabber Registrar considerations and XML schema.
> (psa/jp/ip/jk)


Some notes:

§3.1.2
| The server also remembers that the requesting resource is "save-mode aware"
| and will broadcast it any changes in the Save Mode state. 

Sometimes, the client may have requested that information but not require to 
be notified of changes.  (example, if it just use it in the config dialog, 
but doesn't cache the data)  (same would be true with the jabber:iq:private 
if broadcasting change is ever implemented)
maybe a flag could be set in order to request to be notified of change when 
requesting.
This is probably not really important since it is not supposed to change 
often, and will not consume lot of brandwith, 


§3.1.4 Toggling Save Mode State for a Contact

I would add the possibility to do save="default" which remove the item
It could also be nice to allow to enable/disable encryption by group


About OTR:
The contact should be able to refuse the OTR mode.


What about searching ? is it out of the scope of this JEP ?
 
Maybe JEP-0059 (Result Set Manipulation)  could be used when receiving 
message. (instead of maxitems='50' and partial='true')

Another information that could be nice is the list of collection *modified* 
since a certain date, in order to allow synchronization.

--
Olivier (aka Gof)
Mail/JID: ogoffart at kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060504/b0fdba8d/attachment.sig>


More information about the Standards mailing list