Re: support git+mosh for unreliable connections

From: Andreas Krey <a.krey@gmx.de>
Date: Apr 22, 2015, 06:54 UTC
Message-ID: <20150422065405.GB11889@inner.h.apk.li>
In-Reply-To: <1429125944.16649.2.camel@kaarsemaker.net>

On Wed, 15 Apr 2015 21:25:44 +0000, Dennis Kaarsemaker wrote: ...

Show 7 quoted lines

> It does not and cannot work. The way mosh works, is that it uses ssh to
> log in and launch a mosh-server daemon. This daemon and the mosh client
> then communicate via a custom UDP protocol. The SSH connection is closed
> after the mosh-server has been launched as it is no longer needed.
> 
> The communication between the mosh client and server synchronizes
> terminal state, somewhat like what screen/tmux do.

I object to the 'can not' part a bit. There is (1) the terminal state prediction and (2) the reliable-over-reconnects communication, and for a noninteractive usage you'd need only (2).

Once upon a time I implemented a simple UDP server and client; the client to be used as a ProxyCommand in ssh, and the server just talks to the local ssh server. This pretty much does what the OP wants, and it works just as a transport for ssh, so all ssh features are there (but of course there is no terminal prediction). Unfortunately it needs to be ported to libev/libuv before it could be released. It's *much* simpler than mosh, although the use-ssh-to-start-server trick would be nice.)

Andreas

-- 
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800