2011-05-17 16:14:46 +00:00
|
|
|
[[forum/tips:_special__95__remotes__47__hook_with_tahoe-lafs]] is a good
|
|
|
|
|
start, but Zooko points out that using Tahoe's directory translation layer
|
|
|
|
|
incurs O(N^2) overhead as the number of objects grows. Also, making
|
|
|
|
|
hash subdirectories in Tahoe is expensive. Instead it would be good to use
|
|
|
|
|
it as a key/value store directly. The catch is that doing so involves
|
|
|
|
|
sending the content to Tahoe, and getting back a key identifier.
|
|
|
|
|
|
2011-05-17 16:18:50 +00:00
|
|
|
This would be fairly easy to do as a [[backend|backends]], which can assign its
|
2011-05-17 16:14:46 +00:00
|
|
|
own key names (although typically done before data is stored in it),
|
|
|
|
|
but a tahoe-lafs special remote would be more flexible.
|
|
|
|
|
|
|
|
|
|
To support a special remote, a mapping is needed from git-annex keys to
|
2014-01-09 00:01:12 +00:00
|
|
|
Tahoe keys, stored in the git-annex branch.
|
2011-05-17 16:14:46 +00:00
|
|
|
|
2014-04-01 00:53:16 +00:00
|
|
|
> This is now done, however, there are 3 known
|
2014-01-09 00:01:12 +00:00
|
|
|
> problems:
|
|
|
|
|
>
|
|
|
|
|
> * tahoe start run unncessarily <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2149>
|
|
|
|
|
> * web.port can conflict <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2147>
|
2014-04-01 00:53:16 +00:00
|
|
|
> * Nothing renews leases, which is a problem on grids that expire.
|
|
|
|
|
> <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2212>
|
|
|
|
|
|
2014-01-09 00:01:12 +00:00
|
|
|
> --[[Joey]]
|
