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

avoid populating proxy's object file when storing on special remote

Browse source 
Now that storeKey can have a different object file passed to it, this
complication is not needed. This avoids a lot of strange situations,
and will also be needed if streaming is eventually supported.
This commit is contained in:
Joey Hess 2024-07-01 10:53:49 -04:00
parent 8b5fc94d50
commit dce3848ad8
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
2 changed files with 12 additions and 53 deletions
Download patch file Download diff file Expand all files Collapse all files

11
doc/todo/git-annex_proxies.mdwn
View file

@ -34,17 +34,6 @@ For June's work on [[design/passthrough_proxy]], remaining todos:
* If GET from a proxied special remote sends an ERROR with a message
from the special remote, currently the user sees "protocol error".
* convert Remote.storeKey to take the path of the object file to send.
It's too ugly that PUT to a proxied special remote currently has to
temporarily populate the proxy's annex object file. There are too many
ways that could lead to surprising behavior, like an interrupted PUT
leaving it populated, or simulantaneous PUTs.
* PUT to a proxied special remote, in the case where the proxy contains
the key, and the special remote is not accessible, sends back ERROR
rather than PUT-FROM or ALREADY-HAVE. Verify that the client processes
that ok and displays it to the user.
* Streaming download from proxied special remotes. See design.
* Check annex.diskreserve when proxying for special remotes.