From 5c2c15b7cc7250fe5ea566d17713c12abd11bfc5 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 21 Jun 2010 19:08:44 +0000 Subject: [PATCH] 1.2, with Council note git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@4255 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0136.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/xep-0136.xml b/xep-0136.xml index dfc45cc7..e10195c0 100644 --- a/xep-0136.xml +++ b/xep-0136.xml @@ -46,10 +46,10 @@ asterix@lagaule.org - 1.2rc1 - in progress, last updated 2010-01-06 + 1.2 + 2010-06-21 at/yl -

Added persistent auto save setting; added ability to control settings per chat session.

 +

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.

 1.1 @@ -174,6 +174,7 @@ +

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.

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.

There are two main approaches to this problem: