From: Dennis Kaarsemaker <dennis@kaarsemaker.net>
To: Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: Trevor Saunders <tbsaunde@tbsaunde.org>,
Pirate Praveen <praveen@debian.org>,
Michael J Gruber <git@drmicha.warpmail.net>,
git@vger.kernel.org, git-owner@vger.kernel.org
Subject: Re: support git+mosh for unreliable connections
Date: Wed, 15 Apr 2015 21:25:44 +0200 [thread overview]
Message-ID: <1429125944.16649.2.camel@kaarsemaker.net> (raw)
In-Reply-To: <31749ad9ba57ada7f9c553191ffaddb3@www.dscho.org>
On wo, 2015-04-15 at 19:46 +0200, Johannes Schindelin wrote:
> On 2015-04-15 17:33, Trevor Saunders wrote:
> > but it certainly does support ssh <host> <command>
> > and then doing IO.
>
Yes, in interactive sessions. mosh synchronizes terminal state, it
doesn't allow random I/O between client and server.
> Ah, so mosh's README lied to me!
>
> If `mosh <user>@<host> <command>` works, then a simple `GIT_SSH=mosh`
> should work out of the box, too. Have you tried it?
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.
--
Dennis Kaarsemaker
www.kaarsemaker.net
next prev parent reply other threads:[~2015-04-15 19:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 13:07 support git+mosh for unreliable connections Pirate Praveen
2015-04-15 13:45 ` Dennis Kaarsemaker
2015-04-15 13:52 ` Michael J Gruber
2015-04-15 14:18 ` Pirate Praveen
2015-04-15 14:41 ` Johannes Schindelin
2015-04-15 15:33 ` Trevor Saunders
2015-04-15 17:46 ` Johannes Schindelin
2015-04-15 18:59 ` Trevor Saunders
2015-04-16 9:29 ` Michael J Gruber
2015-04-15 19:25 ` Dennis Kaarsemaker [this message]
2015-04-22 6:54 ` Andreas Krey
2015-04-15 14:22 ` Johannes Schindelin
2015-04-15 14:43 ` Pirate Praveen
2015-04-15 20:26 ` Ilari Liusvaara
2015-04-20 8:39 ` Pirate Praveen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1429125944.16649.2.camel@kaarsemaker.net \
--to=dennis@kaarsemaker.net \
--cc=git-owner@vger.kernel.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=praveen@debian.org \
--cc=tbsaunde@tbsaunde.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).