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

comment

Browse source
This commit is contained in:
Joey Hess 2022-09-16 12:39:43 -04:00
parent 43a1f34094
commit 0a4871cb65
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 23 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
doc/todo/Special_remotes__58___support_for_MULTIREMOVE/comment_7_993ed66935c0d95488751a0e0e2c57b8._comment Normal file
View file

@ -0,0 +1,23 @@
[[!comment format=mdwn
username="joey"
subject="""comment 7"""
date="2022-09-16T16:27:58Z"
content="""
> I'm not sure if there are use-cases where this additional information is useful to the remote
It would be useful when the actions transfer content, since the remote
could look at the key sizes and accumulate a reasonable amount of data
for it to handle in one operation.
>> This is more complicated
By that I meant, it's more complicated for the poor author of the external
special remote, who has to learn about the async protocol.
But not using the async protocol will always have the problem I discussed
in comment #5, since the implementation in git-annex is always
to send a command like REMOVE and wait for a response like REMOVE-SUCCESS.
Using the async protocol lets it keep that implementation simple, by
multiplexing the multiple removes into different jobs, which when
demultiplexed look the same as a single remove looks now.
"""]]