On Thu, Jul 7, 2011 at 9:13 AM, Laurence Rowe <l...@lrowe.co.uk> wrote: > On 6 July 2011 19:44, Jim Fulton <j...@zope.com> wrote:
... > Adding the ability to store blobs in S3 would be an excellent feature > for AWS based deployments. I'm not convinced that presenting S3 urls > to the end users is terribly useful as there is no ability to set a > Content-Disposition header and the url will not end with the correct > file extension, which will cause problems for users downloading files. My lack of S3 foo is showing. > I would imagine a more common setup would be to serve the S3 stored > blobs through a proxy server running in EC2, using something similar > to Nginx's X-Accel-Redirect. Lovely Systems has some information on > generating an S3 Authrorization header in Nginx here: > http://www.lovelysystems.com/nginx-as-an-amazon-s3-authentication-proxy-2/ > - though generating an authenticated S3 URL in Python to set in the > X-Accel-Redirect header would lead to much simpler proxy > configuration. I'll have to do some more digging and get back. > In either case though, I don't see why doing so would necessitate > changing the blob record format - presumably a blob's url can be > simply mapped from the S3 blobstorage configuration and a blob's oid > and tid? You're probably right. That's a much better approach. Jim -- Jim Fulton http://www.linkedin.com/in/jimfulton _______________________________________________ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org https://mail.zope.org/mailman/listinfo/zodb-dev
