Jeff: Replies inline
On Sat, Jun 8, 2013 at 9:49 AM, Jeff Schnitzer <[email protected]> wrote: > > > Some questions: > > * Will the current upload mechanism be preserved? Looking through the > docs it appears the answer is that you create a signed url directly into > GCS and have the client POST/PUT it, which seems like it should be > compatible with the existing BlobstoreService.getUploadUrl() approach. But > how do we get notification when the upload is complete? Right now the > blobstore upload mechanism gives us a callback, and I do important things > on this callback. > This will continue to function as it does now. This api is not affected. > * Will this work with the image service the way the blobstore does now? I > transform, resize, and crop images on the fly - this rarely-lauded feature > is actually one of my favorite parts of GAE. > Yes. In fact you can already use the image service with files in GCS and blobstore using the same API. > * Will existing blobstore-based image urls be preserved? I have a lot of > these in my datastore. > Today's announcement will have no effect on files store in blobstore. > * What does the GAE dev environment do with the GCS apis? What about the > Local Unit Testing framework? > It will work and use local disk as the backing store. > As long as there are sane answers to these questions, I have no objection > to GCS... although it will require that I rewrite and some code: > > * I read PDF data out of the blobstore using the files api, send it off > to a service for transformation into an image, then write the image back to > the blobstore. This sounds pretty straightforward with GCS. > > * I de-dup all uploaded images using the hash, and track image > references. This means I have a lot of data referencing BlobKeys in the > datastore. This brings up the question, if data is migrated from Blobstore > to GCS, what are the new keys? Will it be clear how to migrate this data? > You can generate a BlobKey from an Item in GCS so this code would not need to be changed much. Data migration is not being done, nor is it necessary for you to plan for at this time. > I don't object to rewriting code as long as the migration path is clear. I > can appreciate consolidating development effort around a single > blobstore-ish offering. > > Thanks, > Jeff > > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
