aboutsummaryrefslogtreecommitdiff
path: root/Remote/P2P.hs
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2018-03-08 14:02:18 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2018-03-08 15:11:31 -0400
commit9c1fb9d7822efadae1027c9763e2bf573399d0b3 (patch)
tree873811f61c835336e6774cff252ab00f2da18f1f /Remote/P2P.hs
parent6637d79273a84c83fa13bb5d797d4dcee07c363e (diff)
p2p ssh connection pools
Much like Remote.P2P, there's a pool of connections to a peer, in order to support concurrent operations. Deals with old git-annex-ssh on the remote that does not support p2pstdio, by only trying once to use it, and remembering if it's not supported. Made p2pstdio send an AUTH_SUCCESS with its uuid, which serves the dual purposes of something to detect to see that the connection is working, and a way to verify that it's connected to the right uuid. (There's a redundant uuid check since the uuid field is sent by git_annex_shell, but I anticipate that being removed later when the legacy git-annex-shell stuff gets removed.) Not entirely happy with Remote.Git.runSsh's behavior when the proto action fails. Running the fallback will work ok, but what will we do when the fallbacks later get removed? It might be better to try to reconnect, in case the connection got closed. This commit was sponsored by Boyd Stephen Smith Jr. on Patreon.
Diffstat (limited to 'Remote/P2P.hs')
-rw-r--r--Remote/P2P.hs6
1 files changed, 2 insertions, 4 deletions
diff --git a/Remote/P2P.hs b/Remote/P2P.hs
index 83ce258de..cfed5c604 100644
--- a/Remote/P2P.hs
+++ b/Remote/P2P.hs
@@ -116,10 +116,8 @@ lock u addr connpool k callback =
go False = giveup "can't lock content"
go True = withVerifiedCopy LockedCopy u (return True) callback
--- | A connection to the peer.
-data Connection
- = OpenConnection P2PConnection
- | ClosedConnection
+-- | A connection to the peer, which can be closed.
+type Connection = ClosableConnection P2PConnection
type ConnectionPool = TVar [Connection]