Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

XEP-0060: Explicitely say that items are returned in chronological or… #1124

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+9 −0
Open

XEP-0060: Explicitely say that items are returned in chronological or… #1124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions xep-0060.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,12 @@
&pgmillard;
&stpeter;
&ralphm;
<revision>
<version>1.22.1</version>
<date>2021-11-06</date>
<initials>jp</initials>
<remark><p>Explicitely say that items are returned in chronological order.</p></remark>
</revision>
<revision>
<version>1.22.0</version>
<date>2021-09-07</date>
Expand Down Expand Up @@ -2215,6 +2221,7 @@ And by opposing end them?
</section3>
<section3 topic='Returning All Items' anchor='subscriber-retrieve-returnall'>
<p>The service then SHOULD return all available items at the node, although it MAY truncate the result set if a large number of items has been published (see next section) and naturally it cannot return items that have been deleted, expired, etc.</p>
<p>By default, items are returned in chronological order (from oldest published to most recent published). This order can be explicitely modified by an extensions like &xep0413;.</p>
<example caption='Service returns all items'><![CDATA[
<iq type='result'
from='pubsub.shakespeare.lit'
Expand Down Expand Up @@ -2291,6 +2298,7 @@ And by opposing end them?
<section3 topic='Returning Some Items' anchor='subscriber-retrieve-returnsome'>
<p>A node may have a large number of items associated with it, in which case it may be problematic to return all of the items in response to an items request. In this case, the service SHOULD return some of the items and note that the list of items has been truncated by including a &xep0059; notation.</p>
<p>A Pubsub entity supporting &xep0059; SHOULD include a feature of "http://jabber.org/protocol/pubsub#rsm" in its disco#info response, to make it clear that the RSM feature is for PubSub, and not for e.g., &xep0313;.</p>
<p>In the same way as for <link url="#subscriber-retrieve-returnal">Returning All Items</link>, items are by default returned in chronological order globally and inside pages. This order can be modified by extensions such as &xep0413;.</p>
<example caption='Service returns some items via result set management'><![CDATA[
<iq type='result'
from='pubsub.shakespeare.lit'
Expand Down Expand Up @@ -2439,6 +2447,7 @@ O, what a rogue and peasant slave am I!
</section3>
<section3 topic='Requesting the Most Recent Items' anchor='subscriber-retrieve-requestrecent'>
<p>A service MAY allow entities to request the most recent N items by using the 'max_items' attribute. When max_items is used, implementations SHOULD return the N most recent (as opposed to the N oldest) items. (Note: A future version of this specification may recommend the use of <cite>XEP-0059</cite> instead of the 'max_items' attribute.)</p>
<p>Like for <link url="#subscriber-retrieve-returnal">Returning All Items</link> and <link url="#subscriber-retrieve-returnsome">Returning Some Items</link>, items are returned in chronological order.</p>
<example caption='Subscriber requests two most recent items'><![CDATA[
<iq type='get'
from='[email protected]/barracks'
Expand Down