On Tue, Mar 3, 2015 at 8:56 AM, Mihai Moldovan <io...@ionic.de> wrote:
> On 03.03.2015 03:36 PM, Michael DePaulo wrote:
>> I feel awkward asking these since I am a developer.
>>
>> 1. What are the differences between a session that is "suspend" and a
>> session that is "running" but disconnected?
>
> A suspended session has been gracefully suspended within the client.
>
> A running session could either be an active one currently used, or one
> that is still waiting for a timeout of the client crashed or the
> connection was dropped prematurely for any reason.
> Running sessions should switch into suspended state after a (rather
> long?) timeout.
>
> You cannot attach to running sessions, but you can forcefully suspend a
> running session from the client and then attach to it.
Is there some reason for that? I preferred the NX/freenx approach
where the new connection would automatically grab the existing session
(since you obviously wouldn't be trying to reconnect if you already
had a running client on the computer you are currently using).
> If there is a suspended session, there multiple two cases:
> 1.) the session you currently want to start matches the already
> existing, suspended session (same settings, including the
> "application"/"desktop" to start) => this session will then be attached
> to without prior notification, you will NOT see the session list beforehand
> 2.) the session to start matches a "running" session on the server.
> You will be presented with the list (and able to forcefully suspend the
> running session, if that's what you're after.)
> 3.) the new session differs in session setting details. In this case,
> you will get the session list.
>
> I don't like this, because it's inconvenient if you explicitly want to
> start a new session with the same characteristics. In my opinion, the
> session list should always be provided if one session (no matter the
> settings or state) is running on the server.
I disagree - I _always_ want to reconnect to my existing session,
across different clients and I'd rather not have to do unnecessary
work suspending/retrying or picking one session from a list of one
just because my laptop and mac screen sizes don't match my windows
desktop where the session was likely started. If you are going to
change this behavior, can you please make it configurable so people
who only start one desktop session per host can always reconnect
without extra confusion, including automatically grabbing the session
you forgot to suspend before leaving your desk?
Aside from always wanting access to my same set of open windows and
long-running programs, I've had problems with some desktop
environments and GUI applications with concurrent sessions for the
same user. Some of them maintain hidden files that don't handle
concurrent updates gracefully, and some (like firefox) may try to open
a new instance as a new window in an already running session (which
may not be the one you are displaying). So - starting a new session
if you already have one just seems wrong, especially if the session is
of the same desktop environment type.
--
Les Mikesell
lesmikes...@gmail.com
_______________________________________________
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user
