On Wed, Apr 30, 2014 at 9:55 AM, Lamar Owen lowen@pari.edu wrote:
That hasn't been a reasonable assumption for anything running X, ever, and even less so with freenx/x2go.
Interestingly, X turns the whole client/server thing on its head..... and always has.
But freenx/NX/x2go put the big picture back the way it belongs. That is both ends run proxy/caching stubs that can disconnect and reconnect from each other without breaking things. The host running the desktop (what you think of as the server) also runs a proxy X display server. The host with the physical display (what you think of as a client) runs a proxy client and server,
You want the applications on a stable, stably networked server and the displays out where people work.
So, pardon the logic, you want the clients running on reliable servers and the servers running on the remote clients. (Yes, I know what I just said..... it's supposed to be humorous......). But think about cloud desktops for a moment, and think about dynamic cloud desktop service mobility that follows you (network-wise, for lowest latency) to give you the best user experience. (No, VDI is not doing this seamlessly yet).
If you've never used NX or x2go, try it. You really do want that caching/proxy layer to deal with network latency and give you the ability to disconnect and pick up your still-running session from a different client - and I mean client in the logical sense. X2go even has a handy way to set up remote rdp sessions to windows targets over its ssh tunnel and caching layer.