aboutsummaryrefslogtreecommitdiff
path: root/doc/todo/accellerate_ssh_remotes_with_git-annex-shell_mass_protocol.mdwn
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo/accellerate_ssh_remotes_with_git-annex-shell_mass_protocol.mdwn')
-rw-r--r--doc/todo/accellerate_ssh_remotes_with_git-annex-shell_mass_protocol.mdwn4
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/todo/accellerate_ssh_remotes_with_git-annex-shell_mass_protocol.mdwn b/doc/todo/accellerate_ssh_remotes_with_git-annex-shell_mass_protocol.mdwn
index ff4b8c59d..a592e17a9 100644
--- a/doc/todo/accellerate_ssh_remotes_with_git-annex-shell_mass_protocol.mdwn
+++ b/doc/todo/accellerate_ssh_remotes_with_git-annex-shell_mass_protocol.mdwn
@@ -40,3 +40,7 @@ Implementation todos:
git-annex-shell recvkey has a speed optimisation, when it's told the file
being sent is locked, it can avoid an expensive verification.
* Maybe similar for transfers in the other direction?
+* What happens when the assistant is running and some connections are open
+ and it moves between networks?
+* If it's unable to ssh to a host to run p2pstdio, it will fall back to the
+ old method. What if the host is down, does this double the timeout?