[FreeNX-kNX] Re: Resuming NX Session from different machine]

[Gian Filippo Pinzari]

Rick Stout wrote:
> Two things. I dont think it's possible to resume a suspended session on 
> a different machine. The client store some connections information that 
> another machine cannot get. 

It is actually possible to resume a session on another machine,
but there are some constraints. For example the depth of the X
server must be matched and the core fonts that were in use at
the time the session was suspended must exist on the new client.
These limitations are not that serious (most users have 32 bpp
displays and they only use client-side fonts, thanks to the
RENDER extension) but there is one limitation that is really
annoying. It is more a bug, related to the way NX sessions are
run on Windows, than a real constraint.

NX desktops on Windows are created as full-screen windows, inside
their own X server. This is due to the poor support for the multi-
window mode of operation in the current Cygwin X server. When re-
connecting the session on Linux, the client will try to match the
full-screen attribute. If the geometry of the virtual desktop
doesn't match the geometry of the Linux X server, resuming the
session will not be possible. This is not a NX server problem. It
is the nxagent component that will fail to migrate the session
the new X server.

What to do:

First of all the full-screen attribute must become a run-time
attribute, so that a session can be created in a top-level window
and switched to full-screen by pressing a key-sequence. Secondly
it must be possible to resize the virtual desktop window. Even if
creating scroll-bars is not an easy task, users should be able to
move the viewable part by dragging the desktop using the keyboard
or the mouse. These changes are very easy to do. Expect them as
part of the future NX OSS releases.

/Gian Filippo.