Mercurial > libervia-backend
view doc/libervia-cli/remote-control.rst @ 4306:94e0968987cd
plugin XEP-0033: code modernisation, improve delivery, data validation:
- Code has been rewritten using Pydantic models and `async` coroutines for data validation
and cleaner element parsing/generation.
- Delivery has been completely rewritten. It now works even if server doesn't support
multicast, and send to local multicast service first. Delivering to local multicast
service first is due to bad support of XEP-0033 in server (notably Prosody which has an
incomplete implementation), and the current impossibility to detect if a sub-domain
service handles fully multicast or only for local domains. This is a workaround to have
a good balance between backward compatilibity and use of bandwith, and to make it work
with the incoming email gateway implementation (the gateway will only deliver to
entities of its own domain).
- disco feature checking now uses `async` corountines. `host` implementation still use
Deferred return values for compatibility with legacy code.
rel 450
| author | Goffi <goffi@goffi.org> |
|---|---|
| date | Thu, 26 Sep 2024 16:12:01 +0200 |
| parents | 05f01ac1d5b2 |
| children |
line wrap: on
line source
.. _libervia-cli_remote-control: ============================== remote-control: Remote Control ============================== The ``remote-control`` feature allows you to control another device or be controlled by another device. send ==== Send control events to another device. For now, it only sends keyboard events. example ------- Louise wants to control Pierre's device:: $ li remote-control send pierre@example.net receive ======= Use ``receive`` to establish a connection with another device and accept incoming control events. This feature uses the freedesktop.org's Remote Desktop portal, which must be installed on your system and compatible with your platform. On most Wayland-based desktop environments, this portal is usually available. Immediately upon connecting, Libervia CLI requests permission to initiate the remote control session, event if not request has been received yet. This ensures that the connection can be established without requiring manual intervention to authorize access. After a connection has been accepted and terminated, the command quits. ``--verbose, -v`` can be used to show received input events. If you don't expect to share screen, use ``S {yes,no,auto}, --share-screen {yes,no,auto}`` with a value of ``no``. example ------- Louise is expecting Piotr to control her device and wants to automatically accept control from him:: $ li remote-control receive louise@example.org