From e642a594a8fc713c7ffccbdc3d61cc3f288f014a Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Fri, 16 Feb 2007 06:12:39 +0000 Subject: [PATCH] 1.2 published git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@599 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0012.xml | 37 +++++++++++++++++++++++++++++-------- 1 file changed, 29 insertions(+), 8 deletions(-) diff --git a/xep-0012.xml b/xep-0012.xml index 2054d799..5a5e0a2a 100644 --- a/xep-0012.xml +++ b/xep-0012.xml @@ -27,40 +27,40 @@ &temas; &stpeter; - 1.2pre1 - in progress, last updated 2007-02-09 + 1.2 + 2007-02-15 psa - Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; added Implementation Notes and clarified text throughout; added proviso to security considerations regarding client support. +

Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; added Implementation Notes and clarified text throughout; added proviso to security considerations regarding client support; added section on Service Discovery.

1.1 2004-01-22 psa - Editorial revisions. +

Editorial revisions.

1.0 2002-01-22 psa - Changed status to Active. +

Changed status to Active.

0.3 2002-01-14 psa - Made appropriate changes to reflect status as informational. +

Made appropriate changes to reflect status as informational.

0.2 2002-01-04 tjm - Converted to XML format. +

Converted to XML format.

0.1 2001-01-25 jm - Initial version from website. +

Initial version from website.

@@ -132,6 +132,27 @@ ]]>

In this example, the server has been up for a little more than 34 hours.

+ +

In order for a requesting entity to determine if a responding entity supports result set management, it SHOULD send a &xep0030; information request to the responding entity:

+ + + + ]]> + + + ... + + ... + + + ]]> +

The information contained in an IQ reply for this namespace is inherently aambiguous. Specifically, for a bare JID (&BAREJID;) the information is the time since the JID was last connected to its server; for a full JID (&FULLJID;) the information is the time since the resource was last active in the context of an existing session; and for a bare domain the information is the uptime for the server or component. An application must take these differences into account when presenting the information to a human user.