Software /
code /
prosody
File
spec/scansion/pep_pubsub_max.scs @ 12254:5b0c8e499288
modulemanager: Add plugin load filter that reads module metadata from source
Metadata in modules is added using lines formatted as:
--% key: value
Where key is a valid identifier string, and value is also a string (leading
and trailing whitespace are trimmed during parsing).
The initial supported keys are:
--% requires_core_features: feature1, feature2, ...
--% conflicts_core_features: feature1, feature2. ...
These 'features' map to features reported by the new core.features module.
A benefit of this load-time metadata approach compared to e.g. something like
module:requires()/module:conflicts() is that we can continue to look in module
search paths for a suitable module. Aborting an already-loaded module due to
a version conflict would be too late.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Fri, 04 Feb 2022 14:20:00 +0000 |
parent | 11631:6641ca266d94 |
line wrap: on
line source
# PEP max_items=max [Client] Romeo jid: pep-test-maxitems@localhost password: password ----- Romeo connects Romeo sends: <iq type="set" id="pub"> <pubsub xmlns="http://jabber.org/protocol/pubsub"> <publish node="urn:xmpp:microblog:0"> <item> <entry xmlns='http://www.w3.org/2005/Atom'> <title>Hello</title> </entry> </item> </publish> <publish-options> <x xmlns="jabber:x:data" type="submit"> <field type="hidden" var="FORM_TYPE"> <value>http://jabber.org/protocol/pubsub#publish-options</value> </field> <field var="pubsub#persist_items"> <value>true</value> </field> <field var="pubsub#access_model"> <value>open</value> </field> <field var="pubsub#max_items"> <value>max</value> </field> </x> </publish-options> </pubsub> </iq> Romeo receives: <iq type="result" id="pub"> <pubsub xmlns="http://jabber.org/protocol/pubsub"> <publish node="urn:xmpp:microblog:0"> <item id="{scansion:any}"/> </publish> </pubsub> </iq>