aboutsummaryrefslogtreecommitdiffstats
path: root/spec/scansion/pubsub_config.scs
diff options
context:
space:
mode:
authorKim Alvefur <zash@zash.se>2021-10-20 17:32:34 +0200
committerKim Alvefur <zash@zash.se>2021-10-20 17:32:34 +0200
commit5016e666403899202ad8b5775761325ee98cf3b8 (patch)
tree3501ad5624c12e623e68f47c824b366655cbf3bd /spec/scansion/pubsub_config.scs
parent8b769c373d076ea0a678680ef187f83cd0e7d19d (diff)
downloadprosody-5016e666403899202ad8b5775761325ee98cf3b8.tar.gz
prosody-5016e666403899202ad8b5775761325ee98cf3b8.zip
mod_pubsub,mod_pep: Advertise maximum number of items via XEP-0122
Clients would generally be using the "max" symbol instead of discovering this, but this also gets us validation and earlier rejection of out of bounds values.
Diffstat (limited to 'spec/scansion/pubsub_config.scs')
-rw-r--r--spec/scansion/pubsub_config.scs4
1 files changed, 2 insertions, 2 deletions
diff --git a/spec/scansion/pubsub_config.scs b/spec/scansion/pubsub_config.scs
index de3f47da..d06d864e 100644
--- a/spec/scansion/pubsub_config.scs
+++ b/spec/scansion/pubsub_config.scs
@@ -49,7 +49,7 @@ Romeo receives:
<field var="pubsub#type" label="The type of node data, usually specified by the namespace of the payload (if any)" type="text-single"/>
<field var="pubsub#max_items" label="Max # of items to persist" type="text-single">
<validate xmlns="http://jabber.org/protocol/xdata-validate" datatype="pubsub:integer-or-max">
- <range min="1"/>
+ <range min="1" max="256"/>
</validate>
<value>1</value>
</field>
@@ -139,7 +139,7 @@ Romeo sends:
<field var="pubsub#type" type="text-single" label="The type of node data, usually specified by the namespace of the payload (if any)"/>
<field var="pubsub#max_items" type="text-single" label="Max # of items to persist">
<validate xmlns="http://jabber.org/protocol/xdata-validate" datatype="pubsub:integer-or-max">
- <range min="1"/>
+ <range min="1" max="256"/>
</validate>
<value>1</value>
</field>