mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

add todo item

Browse source
This commit is contained in:
Joey Hess 2016-05-23 18:13:03 -04:00
parent 70ecc00f31
commit 7afa487eaa
Failed to extract signature
1 changed files with 21 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
doc/design/external_special_remote_protocol.mdwn
View file

@ -396,3 +396,24 @@ It works like this:
* uuid discovery during INITREMOTE.
* Hook into webapp. Needs a way to provide some kind of prompt to the user
in the webapp, etc.
* When a new "special remote message" is added to this protocol, and a
program wants to use it, an old version of git-annex will reject the
message as unknown, and fail to use the remote with a protocol error.
The program can check `git-annex version`, but that's not very
satisfactory. Version comparison can be hard and
PATH might not point to the same git-annex that's running the program.
One way to fix this would be to make git-annex reply to VERSION
with a PROTOCOLKEYWORDS message listing all the keywords in the
protocol that it knows.
The program could then check if the new message it wants to send is on
the list. PROTOCOLKEYWORDS would be ignored by any program that doesn't
care/know about it; programs are required to send UNSUPPORTED-REQUEST.
I worry that some special remote programs might expect to get only
PREPARE or INITREMOTE after VERSION, so this change would break them.
I mean, they shouldn't.. But a quickly/badly written one might.
Probably want to review all the linked external special remote programs
before doing this.