From: Pirate Praveen <praveen@debian.org>
To: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: support git+mosh for unreliable connections
Date: Wed, 15 Apr 2015 19:48:22 +0530 [thread overview]
Message-ID: <552E732E.20107@debian.org> (raw)
In-Reply-To: <552E6D07.5030903@drmicha.warpmail.net>
[-- Attachment #1: Type: text/plain, Size: 841 bytes --]
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?
>
> Michael
>
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).
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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-15 14:18 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 [this message]
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
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=552E732E.20107@debian.org \
--to=praveen@debian.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.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).