Hi Tom, What's the plan with the existing com.google.appengine.api.files classes? I'm about to start work on some code to access Google Cloud Storage. Should I be using the existing Files API or the GCS client library? Is one method preferred over the other?
I haven't been able to get the Files API to work when running locally. I see your library has a LocalRawGcsServiceFactory for this purpose. This alone seems like a good reason to be using your library. Thanks, Shane. On Wednesday, January 30, 2013 9:15:57 AM UTC+11, Tom Kaitchuck wrote: > > *Greetings, > > We’ve been hard at work on improving access to Google Cloud Storage from > App Engine, and today we’re making the first version of our new Google > Cloud Storage Client Library for App Engine available for developers to > test. This client library contains much of the functionality available in > the Files API, but provides key stability improvements and a better overall > developer experience. In the upcoming months we’ll continue to make > improvements with the goal of making this library the preferred way of > accessing Google Cloud Storage from App Engine. > > To get started, check out our documentation at > https://code.google.com/p/appengine-gcs-client/. > > If you have any questions, comments or feedback please feel free to file > bugs or feature requests at > https://code.google.com/p/appengine-gcs-client/issues/list. > > Thanks for your continued support of App Engine, we look forward to your > feedback! > > Regards, > Tom, on behalf of the Google App Engine Team* > -- 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.
