1.2, with Council note

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@4255 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2010-06-21 19:08:44 +00:00
parent 5d2c8e413c
commit 5c2c15b7cc
1 changed files with 4 additions and 3 deletions

View File

@ -46,10 +46,10 @@
<email>asterix@lagaule.org</email>
</author>
<revision>
<version>1.2rc1</version>
<date>in progress, last updated 2010-01-06</date>
<version>1.2</version>
<date>2010-06-21</date>
<initials>at/yl</initials>
<remark><p>Added persistent auto save setting; added ability to control settings per chat session.</p></remark>
<remark><p>Added persistent auto save setting and ability to control settings per chat session; XMPP Council added a statement regarding a future review and simplification of this protocol.</p></remark>
</revision>
<revision>
<version>1.1</version>
@ -174,6 +174,7 @@
</header>
<section1 topic='Introduction' anchor='intro'>
<p class='box'><em>Notice (2010-06-21): The &COUNCIL; believes that the Message Archiving protocol is unduly complex and will likely request a thorough review and simplification of this specification before advancing it to Final.</em></p>
<p>Many XMPP clients implement some form of client-side message archiving. However, it is not always convenient or even possible to archive messages locally, e.g., because it is easier to keep all archives in one universally accessible place (not scattered around on multiple computers or devices) or because the client operates in a web browser or resides on a mobile device that does not have sufficient local storage for message archiving. In addition, server-side archiving makes it possible to offer new services such as integration of instant messaging and email. Therefore it is beneficial to define methods for server-side archiving of XMPP messages.</p>
<p>There are two main approaches to this problem:</p>
<ol start='1'>