blobstore

The Google App Engine Files API now supports programmatic creation if blobstore blobs. I'm trying this out by attempting to fetch an image over http and store it to the blobstore: file_name = files.blobstore.create(mime_type='image/jpeg') image = urllib2.urlopen(url) with files.open(file_name, 'a') as f: f.write(image) # LINE 142 files.finalize(file_name) blob_key = files.blobstore.get_blob_key(file_name) This code is throwing the error: File "/Users/willmerydith/repos/spam/admin.py", line 142, in post f.write(image) File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources

The following code works perfectly. My only concern is that I wanna convert below to AJAX/alternative, so that it doesn't need to refresh the whole page to submit this request. If possible, to also include loading progress bar etc. <form action="{{ upload_url }}" method="POST" enctype="multipart/form-data"> Upload File: <input type="file" name="file"> <br> <input type="submit" name="submit" value="Submit"> <input type="hidden" name="data1" value="{{ data1 }}"> <input type="hidden" name="data1" value="{{ data2 }}"> </form> sgammon Take a look at some JS solutions for AJAX upload - specifically,

I have an app that allows users to save blobs in the blobstore. I have a schema that does so presently, but I am interested in something simpler and less twisted. For context, imagine my app allows users to upload the picture of an animal with a paragraph describing what the animal is doing. Present schema User calls my endpoint api to save the paragraph and name of the animal in entity Animal . Note: The Animal entity actually has 4 fields ( name , paragraph , BlobKey , and blobServingUrl as String). But the endpoint api only allows saving of the two mentioned. Within the endpoint method, on

I'm working with the blobstore and imagesService in App Engine. I'm wondering how long a URL I get from imagesService.getServingUrl(blobKey) will last. If I'm using this to store a users profile picture, can I store this URL in the user or should I store the BlobKey and get the servingUrl each time i need the picture? The URL will last indefinitely. You should definitely still store the blobkey anyway, though, or you will have no way to delete blobs once you no longer need them, or to get alternate image serving URLs. 来源： https://stackoverflow.com/questions/4643892/how-long-does-url-from

I was wondering if anyone knew how long image urls served back from the google app engine blob store remain valid for? I have been tracking on url that i served an image from the blob store on 1/3/13 and its still there. I am ask specifically so i can cache the image url instead of attempting to serve it repeatedly. If i did this i would still check if the image is there, but how often would i need to check that thanks! They remain valid until either you a. call delete_serving_url , or b. delete the underling blob. 来源： https://stackoverflow.com/questions/14331245/how-long-to-blob-urls-served

I wrote a Google App Engine application that makes use of Blobstore to save programmatically-generated data. To do so, I used the Files API , which unfortunately has been deprecated in favor to Google Cloud Storage. So I'm rewriting my helper class to work with GCS. I'd like to keep the interface as similar as possible as it was before, also because I persist BlobKeys in the Datastore to keep references to the files (and changing the model of a production application is always painful). When i save something to GCS, i retrieve a BlobKey with BlobKey blobKey = blobstoreService.createGsBlobKey("

I've used this question as a template to solve the same problem, but I'm running into issues when posting. I have these components: HTML form with a textbox for the image URL. This posts to... A handler that takes the posted URL, encodes it, and uses urlfetch to post it again to... A separate file upload handler that does the actual saving. Component #3 works fine by itself if I use a file input. But I don't quite understand how to get urlfetch what it needs from just the image URL. My process either times out or gets a 500 response from the final handler. # 1 class URLMainHandler