On Wednesday 15 April 2015 07:52 PM, Johannes Schindelin wrote: > 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.
Attachment:
signature.asc
Description: OpenPGP digital signature