Re: support git+mosh for unreliable connections

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Trevor,

On 2015-04-15 17:33, Trevor Saunders wrote:
> On Wed, Apr 15, 2015 at 04:41:42PM +0200, Johannes Schindelin wrote:
>>
>> On 2015-04-15 16:18, Pirate Praveen wrote:
>> > On Wednesday 15 April 2015 07:22 PM, Michael J Gruber wrote:
>> >> What would that require git to do, beyond taking whatever you tell it
>> >> (using GIT_SSH or _GIT_SSH_COMMAND) to use as a drop in replacement for ssh?
>> >
>> > May be support git+mosh as a protocol, since it is not a drop in
>> > replacement. It is redesigned remote shell. The ideas it uses for
>> > session resumption needs to be reimplemented. This will need support
>> > from git, because it needs server side to be modified. Use SSP to return
>> > the the current progress for a particular session (it uses AES session ids).
>>
>> It will need support from Git alright, but not as much as from mosh, see my other reply: Mosh was not designed for non-interactive use. That support would have to be added before we can go any further.
> 
> is that really relevent? mosh doesn't support things like X forwarding
> or port forwarding, but it certainly does support ssh <host> <command>
> and then doing IO.

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?

Ciao,
Johannes
  It might not support not doing terminal emulation
> stuff, but that seems like a simple thing to change in principal at which
> point I think it would support enough of ssh's functionality its a drop
> in replacement as far as git is concerned.  Seems to me mosh is close
> enough on its own its worth experimentation by someone who cares.
> 
> Trev
> 
>> > So when a client connect with a session id, git server side can respond
>> > with the current state, how many objects received in that session, and
>> > client can continue from where it stopped. Client also will need to
>> > store session information.
>>
>> No, the protocol can stay exactly the same, once you have a way to communicate non-interactively via mosh.
>>
>> Ciao,
>> Johannes
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@xxxxxxxxxxxxxxx
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]