A page in your DokuWiki was added or changed. Here are the details:
Browser : Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101
Firefox/115.0
IP Address : 87.147.72.22
Hostname : p57934816.dip0.t-ipconnect.de
Old Revision :
https://wiki.x2go.org/doku.php/wiki:advanced:x2gokdrive:start?rev=1720469339
New Revision :
https://wiki.x2go.org/doku.php/wiki:advanced:x2gokdrive:start
Date of New Revision: 2024/07/08 20:12
Edit Summary : [2. X2Go KDrive is a real X-Server]
User : uli42
There may be newer changes after this revision. If this
happens, a message will be shown on the top of the rev page.
@@ -19,11 +19,11 @@
* We don't need to support obsolete X code, which makes the development and
support much easier.
* We profit of bugfixes that might be missing in x2goagent
==== 2. X2Go KDrive is a real X-Server ====
- If x2goagent is just a proxy between X-Servers on the server and client
sides, X2Go KDrive is a standalone X-Server. It brings a lot of advantages over
NX-protocol:
- * We don't need an X-Server on the client side. This is a main advantage.
If we want to use NX-Libraries, we always need a fully functional X-Server on
client, like XQuartz on Mac or VCXsrv on Windows. X-applications are not native
to this OS and are always the source of many troubles. Another OS, like Android
or IOS, doesn't have any usable X-Server software at all. Using X2Go KDrive we
can avoid this issue and build native clients for any platform and even develop
HTML5 client.
- * The X2Go KDrive architecture is better suited for the modern application
like Firefox or Chromium. This applications are developed to run on different
platforms and using cross-platform graphic libraries like Skia. Modern browsers
and some other applications working much better with X2Go KDrive than with NX.
+ While x2goagent is some kind of proxy between two X servers (on on the server
and one on client side), X2Go KDrive is a standalone X server. That brings a
lot of advantages over using the NX protocol:
+ * We don't need an X server on the client side. This is the main advantage.
If we want to use NX libraries, we always need a fully functional X server on
the client side (like XQuartz on Mac or VCXsrv on Windows). X applications are
not native to these OSes and are always the source of many troubles. Other
OSes, e.g. Android or IOS, don't have any usable X server implementation at
all. Using X2Go KDrive we can avoid these issues and build native clients for
any platform and even develop an HTML5 client.
+ * The X2Go KDrive architecture is better suited for modern applications
like Firefox or Chromium. These applications are developed to run on different
platforms and are using cross-platform graphic libraries like Skia. Modern
browsers and some other applications working much better with X2Go KDrive than
with NX.
===== How X2Go KDrive works=====
X2Go KDrive works similar to Xephyr with only difference, that it's not
rendering frames in the X-window but transferring them instead over the network
to x2gokdriveclient. x2gokdriveclient running on the client computer, rendering
the frames, capturing the input events and sending them back to the server.
--
This mail was generated by DokuWiki at
https://wiki.x2go.org/
_______________________________________________
x2go-commits mailing list
[email protected]
https://lists.x2go.org/listinfo/x2go-commits
