Mercurial > libervia-backend
view doc/libervia-cli/uri.rst @ 4002:5245b675f7ad
plugin XEP-0313: don't wait for MAM to be retrieved in connection workflow:
MAM retrieval can be long, and can be done after connection, message just need to be
sorted when being inserted (i.e. frontends must do insort).
To avoid blocking connection for too long and result in bad UX and timeout risk, one2one
MAM message are not retrieved in background.
author | Goffi <goffi@goffi.org> |
---|---|
date | Fri, 10 Mar 2023 17:22:45 +0100 |
parents | c80a0f864b5d |
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:: $ li 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:: $ li uri build pubsub somebody@example.org -f node urn:xmpp:microblog:0