Software /
code /
prosody
File
spec/scansion/lastactivity.scs @ 11040:c560531d9a6e
mod_external_services: Validate services added via events
While writing developer documentation it became obvious that i was silly
to have one item format for config and items API, and another format for
the event API.
Then there's the stanza format, but that's a common pattern.
This change reduces the possible input formats to two and allows other
modules the benefit of the processing and validation performed on items
from the config.
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Mon, 17 Aug 2020 00:24:11 +0200 |
parent | 10732:f5d88ad24b30 |
child | 13405:c8f3cfe59e90 |
line wrap: on
line source
# XEP-0012: Last Activity / mod_lastactivity [Client] Romeo jid: romeo@localhost password: password ----- Romeo connects Romeo sends: <presence> <status>Hello</status> </presence> Romeo receives: <presence from="${Romeo's full JID}"> <status>Hello</status> </presence> Romeo sends: <presence type="unavailable"> <status>Goodbye</status> </presence> Romeo receives: <presence from="${Romeo's full JID}" type="unavailable"> <status>Goodbye</status> </presence> # mod_lastlog saves time + status message from the last unavailable presence Romeo sends: <iq id='a' type='get'> <query xmlns='jabber:iq:last'/> </iq> Romeo receives: <iq type='result' id='a'> <query xmlns='jabber:iq:last' seconds='0'>Goodbye</query> </iq> Romeo disconnects # recording ended on 2020-04-20T14:39:47Z