git-annex/CmdLine
Joey Hess 291280ced2
started on git-annex-shell cluster support
Works down to P2P protocol.

The question now is, how to handle protocol version negotiation for
clusters? Connecting to each node to find their protocol versions and
using the lowest would be too expensive with a lot of nodes. So it seems
that the cluster needs to pick its own protocol version to use with the
client.

Then it can either negotiate that same version with the nodes when
it comes time to use them, or it can translate between multiple protocol
versions. That seems complicated. Thinking it would be ok to refuse to
use a node if it is not able to negotiate the same protocol version with
it as with the client. That will mean that sometimes need nodes to be
upgraded when upgrading the cluster's proxy. But protocol versions
rarely change.
2024-06-17 15:10:04 -04:00
..
GitAnnex tab complete special remotes 2024-06-17 09:26:03 -04:00
GitAnnexShell git-annex-shell: accept uuid of remote that proxying is enabled for 2024-06-10 12:44:35 -04:00
Action.hs Fix display when run with -J1 2023-06-15 10:07:54 -04:00
AnnexSetter.hs remove --backend from global options 2022-06-29 13:33:25 -04:00
Batch.hs log migration trees to git-annex branch 2023-12-06 15:40:03 -04:00
GitAnnex.hs broke out initcluster 2024-06-14 17:23:11 -04:00
GitAnnexShell.hs started on git-annex-shell cluster support 2024-06-17 15:10:04 -04:00
GitRemoteAnnex.hs remove dead nodes when loading the cluster log 2024-06-16 14:39:44 -04:00
GitRemoteTorAnnex.hs git-annex-shell: block relay requests 2024-06-10 14:16:27 -04:00
Option.hs initial implementation of --explain 2023-07-25 16:52:57 -04:00
Seek.hs add startAction parameter for KeySha 2023-12-06 13:28:02 -04:00
Usage.hs add FIELD?=GLOB to git-annex view usage 2023-02-07 18:09:10 -04:00