Mercurial > libervia-backend
view doc/libervia-cli/uri.rst @ 3922:0ff265725489
plugin XEP-0447: handle attachment and download:
- plugin XEP-0447 can now be used in message attachments and to retrieve an attachment
- plugin attach: `attachment` being processed is added to `extra` so the handler can inspect it
- plugin attach: `size` is added to attachment
- plugin download: a whole attachment dict is now used in `download` and
`file_download`/`file_download_complete`. `download_uri` can be used as a shortcut when
just a URI is used. In addition to URI scheme handler, whole attachment handlers can now
be registered with `register_download_handler`
- plugin XEP-0363: `file_http_upload` `XEP-0363_upload_size` triggers have been renamed to
`XEP-0363_upload_pre_slot` and is now using a dict with arguments, allowing for the size
but also the filename to be modified, which is necessary for encryption (filename may
be hidden from URL this way).
- plugin XEP-0446: fix wrong element name
- plugin XEP-0447: source handler can now be registered (`url-data` is registered by
default)
- plugin XEP-0447: source parsing has been put in a separated `parse_sources_elt` method,
as it may be useful to do it independently (notably with XEP-0448)
- plugin XEP-0447: parse received message and complete attachments when suitable
- plugin XEP-0447: can now be used with message attachments
- plugin XEP-0447: can now be used with attachments download
- renamed `options` arguments to `extra` for consistency
- some style change (progressive move from legacy camelCase to PEP8 snake_case)
- some typing
rel 379
author | Goffi <goffi@goffi.org> |
---|---|
date | Thu, 06 Oct 2022 16:02:05 +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