25
1
mirror of https://github.com/processone/ejabberd.git synced 2024-11-24 16:23:40 +01:00

PubSub: Bump default value for 'max_items' limit

Bump the default value for mod_pubsub's 'max_items_node' option, which
hard-limits the 'max_items' value requested by clients.

These days, use cases such as microblogging or XEP-0402 may need a large
number of items per node.  Bumping the limit makes sure such
functionality is properly supported with the default configuration.
This commit is contained in:
Holger Weiss 2021-07-28 18:29:19 +02:00
parent 103e98b8da
commit fce7fe8558
2 changed files with 2 additions and 2 deletions

View File

@ -23,7 +23,7 @@
-define(ERR_EXTENDED(E, C), mod_pubsub:extended_error(E, C)). -define(ERR_EXTENDED(E, C), mod_pubsub:extended_error(E, C)).
%% The actual limit can be configured with mod_pubsub's option max_items_node %% The actual limit can be configured with mod_pubsub's option max_items_node
-define(MAXITEMS, 10). -define(MAXITEMS, 1000).
%% this is currently a hard limit. %% this is currently a hard limit.
%% Would be nice to have it configurable. %% Would be nice to have it configurable.

View File

@ -4276,7 +4276,7 @@ mod_doc() ->
#{value => "MaxItems", #{value => "MaxItems",
desc => desc =>
?T("Define the maximum number of items that can be " ?T("Define the maximum number of items that can be "
"stored in a node. Default value is: '10'.")}}, "stored in a node. Default value is: '1000'.")}},
{max_nodes_discoitems, {max_nodes_discoitems,
#{value => "pos_integer() | infinity", #{value => "pos_integer() | infinity",
desc => desc =>