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=1582305094 New Revision : https://wiki.x2go.org/doku.php/wiki:advanced:x2gokdrive:start Date of New Revision: 2024/07/08 20:04 Edit Summary : [Advantages of x2goagent] 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. @@ -8,10 +8,9 @@ The main reason - we want to be able to run modern desktops such as Unity, KDE-5, Gnome-3 and the applications built with the latest toolkits without limitations. ===== What is the difference between x2goagent and X2Go KDrive ===== x2goagent (or nxagent) is based on NX technologies. It's basically kind of X-proxy (like Xnest). It accepting X-protocol requests from X-Client and forwarding them to remote X-Server. In opposite, X2Go KDrive is a real X-Server (like Xephyr). It's processing the requests from X-Client and rendering images on the remote display, like normal X-Server rendering them into the graphic display, using the video driver. You could say, that the difference between x2goagent and X2Go KDrive it's the same as difference between Xnest and Xephyr. ===== Advantages of x2goagent ===== - NX-Protocol using the network transparency of X-protocol. It mean's that instead of sending images over network, it sending the X-requests like "create window" or "move window from one position to another" or "write text in the window". So if you running legacy X-applications, it'll work much faster on the slow networks, than protocols, which are transferring images between server and client. - + x2goagent (also called nxagent) is using the NX protocol, an optimized version of the X protocol. That means that instead of sending images over the network, it forwards the X-requests like "create window" or "move window from one position to another" or "write text in the window". This leads to a very good performance even over slow networks old (legacy X applications). In contrast x2gokdrive does not make use of this protocol and its optimizations. ===== Advantages of X2Go KDrive ===== ==== 1. X2Go KDrive based on the recent X.Org code ==== Unlike the NX-libraries, which are based on obsolete X.Org-6, X2Go KDrive is based on the recent X.Org-7. It brings multiply advantages: * We can run without any limitations any modern Desktops and applications. -- This mail was generated by DokuWiki at https://wiki.x2go.org/
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=1720469046 New Revision : https://wiki.x2go.org/doku.php/wiki:advanced:x2gokdrive:start Date of New Revision: 2024/07/08 20:06 Edit Summary : [Advantages of x2goagent] 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. @@ -7,10 +7,12 @@ ===== Why do we need X2Go KDrive? ===== The main reason - we want to be able to run modern desktops such as Unity, KDE-5, Gnome-3 and the applications built with the latest toolkits without limitations. ===== What is the difference between x2goagent and X2Go KDrive ===== x2goagent (or nxagent) is based on NX technologies. It's basically kind of X-proxy (like Xnest). It accepting X-protocol requests from X-Client and forwarding them to remote X-Server. In opposite, X2Go KDrive is a real X-Server (like Xephyr). It's processing the requests from X-Client and rendering images on the remote display, like normal X-Server rendering them into the graphic display, using the video driver. You could say, that the difference between x2goagent and X2Go KDrive it's the same as difference between Xnest and Xephyr. - ===== Advantages of x2goagent ===== + ===== Advantages and disadvantages of x2goagent ===== x2goagent (also called nxagent) is using the NX protocol, an optimized version of the X protocol. That means that instead of sending images over the network, it forwards the X-requests like "create window" or "move window from one position to another" or "write text in the window". This leads to a very good performance even over slow networks old (legacy X applications). In contrast x2gokdrive does not make use of this protocol and its optimizations. + + On the other hand there is also a disadvantage: x2goagent currently does not support some (nowadays) important X extensions like XInputExtension 2 or Composite. Some modern Desktop Environments require them and can therefor not work on x2goagent. ===== Advantages of X2Go KDrive ===== ==== 1. X2Go KDrive based on the recent X.Org code ==== Unlike the NX-libraries, which are based on obsolete X.Org-6, X2Go KDrive is based on the recent X.Org-7. It brings multiply advantages: * We can run without any limitations any modern Desktops and applications. -- This mail was generated by DokuWiki at https://wiki.x2go.org/
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=1720469183 New Revision : https://wiki.x2go.org/doku.php/wiki:advanced:x2gokdrive:start Date of New Revision: 2024/07/08 20:08 Edit Summary : [1. X2Go KDrive based on the recent X.Org code] 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. @@ -13,11 +13,13 @@ On the other hand there is also a disadvantage: x2goagent currently does not support some (nowadays) important X extensions like XInputExtension 2 or Composite. Some modern Desktop Environments require them and can therefor not work on x2goagent. ===== Advantages of X2Go KDrive ===== ==== 1. X2Go KDrive based on the recent X.Org code ==== - Unlike the NX-libraries, which are based on obsolete X.Org-6, X2Go KDrive is based on the recent X.Org-7. It brings multiply advantages: - * We can run without any limitations any modern Desktops and applications. + Unlike the x2goagent, which is based on a rather old version of the X.Org sample server (somewhere between 7.0/7.1), X2Go KDrive is based on the recent X.Org-7, bringing multiple advantages: + * We can run any modern Desktops and applications without any limitations * 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. -- This mail was generated by DokuWiki at https://wiki.x2go.org/
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/
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=1720469531 New Revision : https://wiki.x2go.org/doku.php/wiki:advanced:x2gokdrive:start Date of New Revision: 2024/07/08 20:14 Edit Summary : [How to use X2Go KDrive] 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. @@ -29,14 +29,14 @@ 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. ===== How to use X2Go KDrive ===== - x2gokdriveclient and x2gokdrive binaries are made to be compatible with nxproxy and x2goagent. You can just rename x2gokdriveclient to nxproxy and x2gokdrive to x2goagent and start the X2Go session using X2Go Client. It works only if X2Go Client is running on Linux. The versions of X2Go Client and X2Go Server, which can run parallel x2goagent and X2Go KDrive sessions are coming soon. + x2gokdriveclient and x2gokdrive binaries are designed as drop-in replacements for nxproxy and nxagent/x2goagent. You can just rename x2gokdriveclient to nxproxy and x2gokdrive to x2goagent and start the X2Go session using X2Go Client. It works only if X2Go Client is running on Linux. Versions of X2Go Client and X2Go Server that can run both x2goagent and X2Go KDrive sessions will come soon. **Please keep in mind:** * This is not a stable software. - * Use it on your own risk and don't use it in productive environment. + * Use it on your own risk and don't use it in productive environments. * At the moment it's only a preview version. We assume you know how X2Go works and you know what are you doing. We don't have a binary builds yet. If you want to try it, you need to build it by yourself or wait until binary packages are ready. -- This mail was generated by DokuWiki at https://wiki.x2go.org/
-
wiki-admin＠x2go.org