moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 18:22:24 -05:00
Code Issues Releases Wiki Activity

XEP-0060: Some wording improvements around the node full cases

Browse Source
This commit is contained in:
Matthew Wild 2023-03-22 13:20:34 +00:00 committed by Maxime “pep” Buquet
parent b8e0a198f9
commit 958a4499db
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
xep-0060.xml
View File

@ -2994,8 +2994,8 @@ And by opposing end them?
]]></example> ]]></example>
</section4> </section4>
<section4 topic='Node is full' anchor='publisher-publish-success-nodefull'> <section4 topic='Node is full' anchor='publisher-publish-success-nodefull'>
<p>If the service or node is configured so that there is a maximum number of items cached at the node and the maximum is reached when an item is published, the service MUST delete one of the existing items.</p> <p>If the service or node is configured so that there is a maximum number of items cached at the node and the maximum is reached when an item is published, the service MUST delete one of the existing items or reject the new item.</p>
<p>The behaviour of the service is reflected through the "pubsub#publish_node_full" option which may take multiple values: "retract-oldest", "discard-oldest", or "reject".</p> <p>The behaviour of the service is determined by the "pubsub#publish_node_full" option which may take one of the following values: "retract-oldest", "discard-oldest", or "reject".</p>
<p>The "retract-oldest" option is the default one and SHOULD be implemented even if this configuration isn't supported.</p> <p>The "retract-oldest" option is the default one and SHOULD be implemented even if this configuration isn't supported.</p>
<p>It is RECOMMENDED for the service to follow the "first in, first out" rule and retract the oldest item. Depending on node configuration, deletion of an existing item MAY result in sending of a retract notification to the subscribers.</p> <p>It is RECOMMENDED for the service to follow the "first in, first out" rule and retract the oldest item. Depending on node configuration, deletion of an existing item MAY result in sending of a retract notification to the subscribers.</p>
<p>When configured as "discard-oldest", a service MUST discard the oldest item.</p> <p>When configured as "discard-oldest", a service MUST discard the oldest item.</p>
@ -3056,7 +3056,7 @@ And by opposing end them?
]]></example> ]]></example>
</section4> </section4>
<section4 topic='Node is full' anchor='publisher-publish-error-nodefull'> <section4 topic='Node is full' anchor='publisher-publish-error-nodefull'>
<p>If the requesting entity attempts to publish an item to a node that has reached its maximum number of items, visible via pubsub#max_items, the service MUST return a &conflict; error, which SHOULD also include a pubsub-specific error condition of &lt;node-full/&gt;, if pubsub#publish_node_full exists and is set to "reject".</p> <p>If the requesting entity attempts to publish an item to a node that has reached its maximum number of items, visible via pubsub#max_items, and the pubsub#publish_full_node configuration value is set to "reject", then the service MUST return a &conflict; error, which SHOULD also include a pubsub-specific error condition of &lt;node-full/&gt;.</p>
<example caption='Entity attempts to publish to a node with max_items reached'><![CDATA[ <example caption='Entity attempts to publish to a node with max_items reached'><![CDATA[
<iq type='error' <iq type='error'
from='pubsub.shakespeare.lit' from='pubsub.shakespeare.lit'