[google-appengine] Re: External Storage Options?

2008-11-03 Thread yejun
Depends on which external service you use. Most likely you will need to proxy credential between different services. Amazon S3 doesn't have per user ACL I believe. The simplest way in mind: you put your s3 credential in your code, when a user request comes in, you check user credential, if verifie

[google-appengine] Re: External Storage Options?

2008-11-03 Thread jivany
Thanks to all of you for all of the info so far! What I was thinking is that you would simply have the GAE app generate the appropriate URL for the external server. I don't really care if the end user sees that the images are coming from another site. What I do care about is ensuring that the U

[google-appengine] Re: External Storage Options?

2008-11-03 Thread yejun
I don't think urlfetch is a good way to get remote object especial large one like images, you will be double charged by network usage. I think HTTP 302 redirect with url based authentication would be a more economical solution. On Nov 3, 12:45 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: >

[google-appengine] Re: External Storage Options?

2008-11-03 Thread [EMAIL PROTECTED]
A solution based off of this : http://stuporglue.org/restrict-access-jpg-htaccess.php on your remote server. Use urlfetch to return and display the images. You'll need to determine the best method for passing off to the remote server that the request is from a validated GAE user, but that should

[google-appengine] Re: External Storage Options?

2008-11-03 Thread yejun
You can use amazon S3 storage for now which support query string authorization. I believe google will offer large file storage in the near future. On Nov 3, 11:19 am, jivany <[EMAIL PROTECTED]> wrote: > Part of me thinks this is a stupid question and I'm over-complicating > the solution but... >

[google-appengine] Re: External Storage Options?

2008-11-03 Thread Barry Hunter
The simplest would probably be just to use incredibably hard to guess URLs - and then the GAE app knows the real url, or how to calcuate it. (eg using md5 hashes with a shared secret) Its not totally secure, people without an account could still access them, if they where given the url, or if the