1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00

XEP-0060: Add a pubsub#rsm disco#info feature to clear confusion

Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2019-08-02 13:50:11 +02:00
parent 4eb97375c4
commit fb71317512
No known key found for this signature in database
GPG Key ID: DEDA74AEECA9D0F2

View File

@ -2236,6 +2236,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'