Software /
code /
prosody
File
spec/scansion/pep_pubsub_max.scs @ 13439:1e229d710a3c
util.signal: Add support for signalfd(2) on Linux
signalfd allows handling signal events using the same method as sockets,
via file descriptors. Thus all signal dispatch can go through the same
main event loop as everything else, removing need for thread-scary
signal handling where execution would just jump to the signal handler
regardless of the state of Lua, and needing to keep track of Lua
states/threads.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Sat, 24 Feb 2024 00:05:29 +0100 |
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>