summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2011-05-13 23:05:14 -0400
committerGravatar Joey Hess <joey@kitenet.net>2011-05-13 23:05:14 -0400
commite72c1c33ae60f7fe544acd0a1f1331138b880e22 (patch)
tree830fedea3f60f6b203b03b3229734c58f178913c /doc/todo
parent536036cfa2c1b28932f72408f1244f8e345eba82 (diff)
would be nice..
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/support_S3_multipart_uploads.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/todo/support_S3_multipart_uploads.mdwn b/doc/todo/support_S3_multipart_uploads.mdwn
new file mode 100644
index 000000000..711ac41b2
--- /dev/null
+++ b/doc/todo/support_S3_multipart_uploads.mdwn
@@ -0,0 +1,14 @@
+Did not know of this when I wrote S3 support. Ability to resume large
+uploads would be good.
+
+<http://aws.typepad.com/aws/2010/11/amazon-s3-multipart-upload.html>
+
+Also allows supporting files > 5 gb, a S3 limit I was not aware of.
+
+NB: It would work just as well to split the object and upload the N parts
+to S3, but not bother with S3's paperwork to rejoin them into one object.
+Only reasons not to do that are a) backwards compatability with
+the existing S3 remote and b) this would not allow accessing the content
+in S3 w/o using git-annex, which could be useful in some scenarios.
+
+--[[Joey]]