Hi Max The issue for us would be that we now have millions of images written to Blobstore, all with publicly facing URLs... moving those to Cloud Storage would likely be expensive and disruptive unless Google can automatically manage that for us.
What I would hate is to have to run 2 systems in parallel: 1 legacy, 1 "shiny new object". Mike :-) On Friday, June 7, 2013 5:18:02 AM UTC+8, Max Ross wrote: > > Hi Jon, > > The alternative is to programmatically write to Google Cloud Storage. Can > you tell me why it's important to write to Blobstore versus GCS? > > Thanks, > Max > > > On Thu, Jun 6, 2013 at 1:41 AM, jon <jonni...@gmail.com <javascript:>>wrote: > >> Chris and Tom, >> >> I absolutely need programmatic write access to Blobstore, and the Files >> API is what I'm using at the moment. What alternative will we have? >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Google App Engine" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/google-appengine/zzpFI5PQbLI/unsubscribe?hl=en >> . >> To unsubscribe from this group and all its topics, send an email to >> google-appengi...@googlegroups.com <javascript:>. >> To post to this group, send email to >> google-a...@googlegroups.com<javascript:> >> . >> Visit this group at http://groups.google.com/group/google-appengine?hl=en >> . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
