Noah Treuhaft 63468ef4a8 Use multipart upload API in S3 Move method ... This change to the S3 Move method uses S3's multipart upload API to copy objects whose size exceeds a threshold. Parts are copied concurrently. The level of concurrency, part size, and threshold are all configurable with reasonable defaults. Using the multipart upload API has two benefits. * The S3 Move method can now handle objects over 5 GB, fixing #886. * Moving most objects, and espectially large ones, is faster. For example, moving a 1 GB object averaged 30 seconds but now averages 10. Signed-off-by: Noah Treuhaft <noah.treuhaft@docker.com>		2016-08-16 10:53:24 -07:00
..
api	Document TOOMANYREQUESTS error code	2016-07-12 12:18:54 -06:00
auth	Merge pull request #1686 from marcusmartins/nbf-leeway	2016-07-19 17:41:57 -07:00
client	Merge pull request #1757 from miminar/cross-mount-middleware-repository	2016-07-19 17:43:10 -07:00
handlers	Stop ErrFinishedWalk from escaping from Repositories walk	2016-08-05 17:21:48 -07:00
listener	[Server] Listen and serve on a unix socket	2015-05-11 16:00:14 +03:00
middleware	Add support for blobAccessController middleware	2016-05-19 14:02:15 +02:00
proxy	when deploy registry as a pull through cache ,function copeContent() may cause a socket leak when docker user canceled its pull operation.	2016-08-02 11:10:10 +08:00
storage	Use multipart upload API in S3 Move method	2016-08-16 10:53:24 -07:00
doc.go	Move initialization code from main.go to the registry package	2015-09-09 14:39:31 -07:00
registry.go	Add support for Let's Encrypt	2016-06-13 11:30:42 -07:00
root.go	Remove signature store from registry. Return a generated signature for manifest	2016-05-27 13:19:26 -07:00