Mercurial > libervia-backend
view doc/libervia-cli/uri.rst @ 3913:944f51f9c2b4
core (xmpp): make `send` a blocking method, fix `sendMessageData` calls:
original `send` method is blocking, and it is used as such by Wokkel and thus can't be
changed to an async method easily. However, an Async method is necessary to have an async
trigger at the very end of the send workflow for end-to-end encryption. To workaround
that, `send` is an async method which call `a_send`, an async method which actually does
the sending. This way legacy method can still call `send` while `a_send` can be await
otherwise.
Fix calls to `sendMessageData`: the method now being an `async` one, `ensureDeferred` had
to be used in some calls.
author | Goffi <goffi@goffi.org> |
---|---|
date | Sat, 24 Sep 2022 16:31:39 +0200 |
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