From 28f5b875b3414da5307340ce38c3c9d2d96aa2dd Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Sun, 5 Apr 2009 22:21:39 +0000 Subject: [PATCH] removed incorrect mention of full JID git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@2993 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0136.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0136.xml b/xep-0136.xml index 7109e02c..387290ef 100644 --- a/xep-0136.xml +++ b/xep-0136.xml @@ -874,7 +874,7 @@

Refer to Result Set Management to learn more about the various ways that the pages of the list may be accessed.

-

To request a page of messages from a collection the client sends a <retrieve/> element. The 'with' and 'start' attributes specify the participating full JID and the start time (see XEP-0082). Both attributes MUST be included to uniquely identify a collection.

+

To request a page of messages from a collection the client sends a <retrieve/> element. The 'with' and 'start' attributes specify the JID and the start time (see XEP-0082). Both attributes MUST be included to uniquely identify a collection.

In addition, the client MAY match an exact bare JID &BAREJID; by setting the boolean 'exactmatch' attribute to a value of "true" or "1" &BOOLEANNOTE; -- for details, refer to the Exact JID Matching section of this document.

The client SHOULD use Result Set Management to limit the number of messages returned by the server in a single stanza, taking care not to request a page of messages that is so big it might exceed rate limiting restrictions.