git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: support git+mosh for unreliable connections

From
PPPirate Praveen <praveen@debian.org>
Date
Apr 15, 2015, 14:43 UTC
Message-ID
<552E7927.5030803@debian.org>
In-Reply-To
<20bd52de595018f49eeeea64128e3a77@www.dscho.org>
On Wednesday 15 April 2015 07:52 PM, Johannes Schindelin wrote:
Show 11 quoted lines
> From https://github.com/keithw/mosh:
> 
>> Mosh does not support X forwarding or the non-interactive uses of SSH, including port forwarding.
> 
> In particular it "does not support [...] the non-interactive uses of SSH", which the git+mosh transport would require, though.
> 
> That means that you would have to invest quite a bit of effort into enhancing mosh to *support* the non-interactive uses of SSH before you could start implementing `git-remote-mosh`...
> 
> Ciao,
> Johannes
> 
Q: Are the mosh principles relevant to other network applications?
    We think so. The design principles that Mosh stands for are
conservative: warning the user if the state being displayed is out of
date, serializing and checkpointing all transactions so that if there
are no warnings, the user knows every prior transaction has succeeded,
and handling expected events (like roaming from one WiFi network to
another) gracefully.

Can the ideas be used to resume a pull, push or clone operation? Especially serializing and checkpointing.

Previous: Johannes SchindelinNext: Ilari Liusvaara
Message 13 of 15 in “support git+mosh for unreliable connections”
  1. Pirate PraveenApr 15, 2015
  2. Dennis KaarsemakerApr 15, 2015
  3. Michael J GruberApr 15, 2015
  4. Pirate PraveenApr 15, 2015
  5. Johannes SchindelinApr 15, 2015
  6. Trevor SaundersApr 15, 2015
  7. Johannes SchindelinApr 15, 2015
  8. Trevor SaundersApr 15, 2015
  9. Michael J GruberApr 16, 2015
  10. Dennis KaarsemakerApr 15, 2015
  11. Andreas KreyApr 22, 2015
  12. Johannes SchindelinApr 15, 2015
  13. Pirate PraveenApr 15, 2015
  14. Ilari LiusvaaraApr 15, 2015
  15. Pirate PraveenApr 20, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.