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

draft external backend protocol

Browse source
This commit is contained in:
Joey Hess 2020-07-20 14:05:49 -04:00
parent 172743728e
commit d1300eca2e
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
4 changed files with 252 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/todo/external_backends/comment_11_56224638fde7b46ee6f52211474cd047._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="joey"
subject="""comment 11"""
date="2020-07-20T18:01:27Z"
content="""
Wrote a draft [[design/external_backend_protocol]].
I wonder if it makes sense to require the programs to format and parse
their own keys; git-annex could break up the key and send the peices in.
The advantage though is that this lets a program decide whether or not to
include information like the size and mtime fields in the key or not.
And if more fields ever got added it would not need changes to the
protocol. I guess it's simple enough for format and parse, as shown by the
example shell program that does it.
"""]]