1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-22 01:02:17 -05:00

Merge branch 'merge/xep-0060'

This commit is contained in:
Jonas Schäfer 2019-09-11 17:44:46 +02:00
commit a9520abca0

View File

@ -49,6 +49,12 @@
&pgmillard; &pgmillard;
&stpeter; &stpeter;
&ralphm; &ralphm;
<revision>
<version>1.16.0</version>
<date>2019-09-11</date>
<initials>edhelas</initials>
<remark><p>Add a pubsub#rsm disco#info feature to clear confusion</p></remark>
</revision>
<revision> <revision>
<version>1.15.8</version> <version>1.15.8</version>
<date>2019-06-19</date> <date>2019-06-19</date>
@ -2236,6 +2242,7 @@ And by opposing end them?
</section3> </section3>
<section3 topic='Returning Some Items' anchor='subscriber-retrieve-returnsome'> <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 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>
<example caption='Service returns some items via result set management'><![CDATA[ <example caption='Service returns some items via result set management'><![CDATA[
<iq type='result' <iq type='result'
from='pubsub.shakespeare.lit' from='pubsub.shakespeare.lit'