Mercurial > libervia-backend
view doc/jp/uri.rst @ 3060:730bbed77a89
plugin XEP-0045: join / MAM history improvements:
- fixed use of history_d deferred so MAM history is stored in database as soon as possible
and in right order
- get MAM history with pages of 20 messages instead of 100
- if a message can't be parsed, an error message is logged (with a dump of the stanza),
and the message is ignored, avoiding a crash and the impossibility the join the room at
all
- a new `mucRoomPrepareJoin` signal, containing room jid and profile, is sent when a room
joining is started, this allow better UX as the frontend can show the room immediately,
and lock it with a waiting message until it is fully available. The `mucRoomJoined` is
still sent when the room is fully joined/avaiable, meaning that the frontend can unlock
it and let the user interact with it
author | Goffi <goffi@goffi.org> |
---|---|
date | Fri, 18 Oct 2019 14:45:07 +0200 |
parents | 72583524cfd3 |
children |
line wrap: on
line source
================================ uri: XMPP URI parsing/generation ================================ URI commands are helper to easily parse/build XMPP URIs. parse ===== Parse an XMPP URI, and print different parts. When possible, the ``type`` of URI is shown (e.g. ``pubsub``) and the ``sub_type`` (e.g. ``microblog``). The ``path`` is always displayed (see `RFC 5122 Path section`_ for details). If suitable, you'll also get data like ``node`` (for a PubSub URI). .. _RFC 5122 Path section: https://tools.ietf.org/html/rfc5122#section-2.4 examples -------- Parse a blog URI:: $ jp uri parse "xmpp:somebody@example.org?;node=urn%3Axmpp%3Amicroblog%3A0" build ====== Build an XMPP URI according to arguments. 2 positional arguments are expected: ``type`` and ``path``. For now, only ``pubsub`` type is supported. examples -------- Build XMPP URI for a blog:: $ jp uri build pubsub somebody@example.org -f node urn:xmpp:microblog:0