I think this is a really serious issue, left unexplained

http://stackoverflow.com/questions/18116707/are-blob-keys-for-gcs-entities-safe-to-use-later
The logical result is, they are unsafe

However if they are unsafe, there is no way to serve them from GAE 
practically, current method to serve blobs/gcs items is to use blobstore's 
download handler, however if blob_key's are unsafe that requires a 
create_gs_key operation each time at a download handler, which is really 
impractical (the create_gs_key delay is unknown)

all the gcs / blobstore examples dodge use cases that would be useful, all 
the examples are useless, creates a sample file, gets blob_key, serves it, 
that is pointless, there is no example that creates an url that can be 
served indefinitely ( this is what I'm referring to: 
https://developers.google.com/appengine/docs/python/blobstore/ "Using the 
Blobstore API with Google Cloud Storage" )

my current result is, blob_key's are unsafe, build a blobstore download 
handler that will convert the gs_object_name to a blob_key and serve it 
each time

if there was an easy way to set read permissions to "all" from gae, that 
would be great too, it sounds logical to serve files from the source, 
however as far as I see, there is no API to change permissions? (you can't 
set permissions to folders - a file by file permission system *seems* like 
a must)

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to