Mercurial > libervia-backend
view doc/libervia-cli/pipe.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 | 267e4987b58b |
children |
line wrap: on
line source
================================================== pipe: send/receive data stream through shell pipes ================================================== ``pipe`` commands allow you to send or receive data stream through a Unix shell pipe. Libervia will create a network connection (using XMPP and Jingle) between you an your contact. in == Receive data stream. Data will be send to stdout, so it can be piped out or simply print to the screen. You can specify bare jids of entities to accept stream for, by default all streams are accepted. example ------- Receive a video stream, and redirect it to mpv_ so show the video:: $ li pipe in | mpv - .. _mpv: https://mpv.io/ out === Send data stream. Data comes from stdin, so you may use pipe in something or just write some text. The only expected argument is the full jid of the device where the stream must be piped out. example ------- Send a video to louise:: $ li pipe out louise@example.org/libervia.123 < some_video.webm Send output from ``cal`` command to louise:: $ cal | li pipe out louise@example.org/libervia.123