diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-03-18 09:47:12 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-03-18 09:47:12 -0400 |
| commit | 70a8a3ab711fb266657653177ec58f8234bb716c (patch) | |
| tree | b084b07b3e53b6cdda72c0d8d1a430691d38f675 | |
| parent | 028eb96f408cddab03a4b77709fb6a24806a5e57 (diff) | |
update
| -rw-r--r-- | doc/todo/S3.mdwn | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/todo/S3.mdwn b/doc/todo/S3.mdwn index cb5186b09..3d18527d4 100644 --- a/doc/todo/S3.mdwn +++ b/doc/todo/S3.mdwn @@ -36,3 +36,17 @@ Problem: Then the only way for unused to know what buckets are in use is to see what keys point to them -- but if the last file from a bucket is deleted, it would then not be able to say that the files in that bucket are all unused. Need cached list of recently seen S3 buckets? + +----- + +One problem with this is what key metadata to include. Should it be like +WORM? Or like SHA1? Or just a new unique identifier for each file? It might +be worth having S3 variants of *all* the Backend.File derived backends. + +More blue-sky, it might be nice to be able to union or stack together +multiple backends, so S3BUCKET+SHA1 or S3BUCKET+WORM. That would likely +be hard to get right. + +Less blue-sky, if the S3 capability were added directly to Backend.File, +and bucket name was configured by annex.s3.bucket, then any existing +annexed file could be upgraded to also store on S3. |