[Standards] XEP-0060: max-items (publish-options et al) council action required

Jonas Schäfer jonas at wielicki.name
Sun Oct 6 12:12:44 UTC 2019


On Sonntag, 6. Oktober 2019 13:19:34 CEST Maxime Buquet wrote:
> On 2019/10/06, Daniel Gultsch wrote:
> > Therefor I propose wording for XEP60 that 'clarifies' that max-items 0
> > means unlimited.
> 
> Is there a way to know as a client when we're going to run into the
> limit? Or when we've gone over the limit? Or is the pubsub service just
> overwritting stuff and nobody ever noticies?

That’s an important note, and I think we need a publish-options field which 
tells the server to not drop items silently but instead reject the publish 
operation with conflict or resource-constraint or something like that.

This is also something a PR would be nice for.

kind regards,
Jonas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.jabber.org/pipermail/standards/attachments/20191006/3dbd37cc/attachment.sig>


More information about the Standards mailing list