Mercurial > prosody-modules
view mod_map/README.markdown @ 4876:0f5f2d4475b9
mod_http_xep227: Add support for import via APIs rather than direct store manipulation
In particular this transitions PEP nodes and data to be imported via mod_pep's
APIs, fixing issues with importing at runtime while PEP data may already be
live in RAM.
Next obvious candidate for this approach is rosters, so clients get immediate
roster pushes and other special handling (such as emitting subscribes to reach
the desired subscription state).
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Tue, 18 Jan 2022 17:01:18 +0000 |
parents | d31fa28d9482 |
children |
line wrap: on
line source
--- labels: - 'Stage-Experimental' summary: Prototype MAM summary --- This is a prototype for an experimental archive summary API recently added in [Prosody trunk](https://hg.prosody.im/trunk/rev/2c5546cc5c70). # Protocol ::: {.alert .alert-danger} This is not a finished protocol, but a prototype meant for testing. ::: A basic query: ``` {.xml} <iq id="lx7" type="get"> <summary xmlns="xmpp:prosody.im/mod_map"/> </iq> ``` Answered like: ``` {.xml} <iq type="result" id="lx7"> <summary xmlns="xmpp:prosody.im/mod_map"> <item jid="juliet@capulet.lit"> <count>3</count> <start>2019-02-25T15:48:00+0100</start> <end>2019-08-23T01:39:50+02:00</end> <body>O Romeo, Romeo! wherefore art thou Romeo?</body> </item> </summary> </iq> ``` It can also take dataform and RSM parameters similar to a [filtered MAM query](https://xmpp.org/extensions/xep-0313.html#filter). E.g if the last message you received had an id `09af3-cc343-b409f` then the following query would tell you who sent you messages since: ``` {.xml} <iq id="lx8" type="get"> <summary xmlns="xmpp:prosody.im/mod_map"> <set xmlns="http://jabber.org/protocol/rsm"> <max>10</max> <after>09af3-cc343-b409f</after> </set> </summary> </iq> ```