[X2Go-Dev] Mac Client status

[John A. Sullivan III]

On Tue, 2012-03-06 at 23:12 +0100, Mike Gabriel wrote:
> Hi John,
> 
> On Di 06 Mär 2012 23:00:35 CET "John A. Sullivan III" wrote:
> 
> > On Tue, 2012-03-06 at 22:55 +0100, Mike Gabriel wrote:
> >> Hi guys,
> >>
> >> On Di 06 Mär 2012 18:48:12 CET "John A. Sullivan III" wrote:
> >>
> >> > On Tue, 2012-03-06 at 18:21 +0100, Mihai Moldovan wrote:
> >> >> - sometimes, I have to resume a session, restart the client,
> >> >> suspend the session
> >> >> and resume it again for it to be usable (first time resuming will
> >> >> just close the
> >> >> connection to the server), BUT IIRC this happens on Linux, too,  
> >> so I can't
> >> >> actually blame the OS X part... (plus, it only happens sometimes. :()
> >>
> >> > <snip>
> >> > I have noticed that problem in Linux.  I think it is an SSH timing
> >> > issue.  The connecting, suspending, reconnecting is not actually doing
> >> > anything, I believe, except functioning as a rudimentary clock.  If one
> >> > just waits five minutes after being abruptly disconnected, all
> >> > reconnects fine :( - John
> >>
> >> When writing the connection/tunneling code of python-x2go I observed
> >> something similar. The problem with port forwarding requests (both
> >> reverse or non-reverse) is a situation when (after suspend) the ports
> >> do no get closed properly. We always have to make sure to properly
> >> cancel port forwarding requests before we disconnect from a SSH session.
> > <snip>
> > So how should we respond if the network connection is broken uncleanly,
> > e.g., the WAN or Internet connection drops or the client computer
> > crashes?
> 
> What I do is, I try to connect and if that fails, I try to cancel the  
> port forwarding requests. This mostly works and sometimes also fails.
<snip>
Yes, but that is what we do as users.  What can we do as developers to
detect and correct this situation so users do not have to do this?
Thanks - John