[FreeNX-kNX] Session Resume Ideas

[Jon Severinsson]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi everyone

I have been doing some thinking on resuming.  Currently it seems as if
it is purely random (of course it isn't, but I haven't found the pattern
by try and error) if a session will be automatically resumed, or if the
list of choices will appear, and what sessions is included in the list.
I have been thinking on how I think FreeNX should behave, and the
following is what I came up with:

Logically (that is in our minds, but not necessarily in code) first step
in making a connection (after authentication) is to make a list of
available sessions.
This list should NOT contain any sessions of another type than the
requested (ie if you ask for a 'unix-kde' you should not be offered to
resume a 'unix-gnome' or 'unix-custom').  In the case of a 'unix-custom'
session the requested command should be the same (if I ask for kcontrol
I don't want to resume a ksysguard session), and in the case of a 'vnc'
or a 'windows' session the agent server and username should also be the
same.
As long as the backend doesn't support reconnections in a different
resolution (ie not until 1.5) the list shouldn't contain sessions in a
resolution other than the requested.  After 1.5 is available, this
should be configureable.
If ENABLE_RECONNECT_RUNNING is enabled then this list should contain
running sessions as well as suspended ones.

Now, if ENABLE_AUTORECONNECT (or, in case of nxclient 1.3.x,
ENABLE_AUTORECONNECT_BEFORE_140) is enabled the first session on this
list that is suspended should be resumed.  If no suspended session is on
the list, a new session is automatically created (unless SESSION_LIMIT
or SESSION_USER_LIMIT is reached, in which case the connection will fail).

If ENABLE_AUTORECONNECT is dissabled and the list contains any sessions
at all, the dialog should appear at clientside where the user can choose
between the session on the list and creating a new session (unless
SESSION_LIMIT or SESSION_USER_LIMIT is reached, in which case that
option is disabled).  If the list is empty, a new session should be
created automatically (unless SESSION_LIMIT or SESSION_USER_LIMIT is
reached, in which case the connection will fail).

As of yet I have not been working very much on implementation, my first
order of business is to figure out what should be done, not how to do
it, but if no one has any objections to the proposed scheme I will give
it a try.

Regards
- - Jonno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCbOVeOOpxqcksWu4RAu8XAJ93/p/sRFv/wiLmyxgfeBtcpC4qHQCfQ4vA
PLNX6ddjI8UgDgCvahb1MzM=
=WXLy
-----END PGP SIGNATURE-----