Xpra

xpra or X Persistent Remote Applications is a tool which runs X clients, typically on a remote host, and directs their display to the local machine without losing any state.[2]

Xpra
Original author(s)Nathaniel Smith
Developer(s)Nathaniel Smith, Antoine Martin
Initial releaseFebruary 20, 2008 (2008-02-20)
Stable release
3.0.5[1] / January 8, 2020 (2020-01-08)
Written inPython
Operating systemUnix-like, MS Windows, Mac OS X
Available inEnglish
LicenseGNU General Public License
Websitexpra.org

It differs from standard "X forwarding" in that it allows disconnection and reconnection without disrupting the forwarded application. It differs from VNC and similar remote display technologies in that xpra is rootless: i.e., applications forwarded by xpra appear on the local desktop as normal windows managed by the local window manager, rather than being all "trapped in a box together". Xpra also uses a custom protocol that is self-tuning and relatively latency-insensitive, and thus is usable over worse links than standard X.

The idea for Xpra was inspired after the original author's experience of attempting to use various NX technology based setups.[3]

Operation

The display server manages the INPUT and the OUTPUT for all of its clients. Xpra acts like a compositing window manager

Xpra connects as a compositing window manager to an Xvfb display server. However, instead of combining the window images to present on the screen, it directs the window images into a network connection to the xpra client, where they are displayed on the remote screen. Mind, the server, also supports direct attachment, which makes it behave as a persistent application server. For example, in the case where there is only a X server available at the remote end. It also acts as a window manager for the X server it is running against, but it doesn't actually have any window manager policy built into it. Instead, it takes all the window management requests from the applications, sends them over the wire to the client, who then issues those same requests on the real display, waits for further answer the real window manager gives, and then forwards that answer back to the xpra server. In addition to the normal xpra client, it also supports using an html 5 capable web browser as a client.[4]

gollark: Explain thyself.
gollark: They actually left according to the apiaristic scanner algorithm.
gollark: It used to accidentally log all messages, but I fixed that.
gollark: It's run in the background, so that would *also* have to be persisted to logs.
gollark: My bot is far too popular. It would use too much storage.

See also

  • GNU Screen and tmux - terminal multiplexers for console-mode (text-mode) applications
  • xmove - a tool allows you to move programs between X Window System displays
  • the lbxproxy tool, which allows disconnecting and reconnecting

References

  1. Martin, Antoine (8 January 2020). "[winswitch] [ANNOUNCE] Xpra 3.0.5: many minor fixes, one critical (same one again)". shifter-users@lists.devloop.org.uk (Mailing list). Retrieved 27 January 2020.
  2. Michael Larabel (2013-08-19). "XPRA: Persistent Remote Applications On X". Phoronix.
  3. Smith, Nathaniel (2009-07-25). "Comment #343389". Google releases Neatx NX server. LWN. Retrieved 2009-07-25. ... I was so frustrated that I wrote a competitor, 'xpra'.
  4. Williams, Al (31 March 2017). "Linux-Fu: Applications on the web". Hackaday. Retrieved 28 September 2018.


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.