[google-appengine] Re: Issue with Cloud Storage GCS API on local Development Server

2013-12-20 Thread Gary Mort
On Tuesday, November 19, 2013 3:57:09 PM UTC-5, k...@form-runner.com wrote: > > I've encountered a problem using the Google Cloud Storage GCS Client API, > running on the local development server. I'm trying to write the bytes > from a PDF file, and then read them back. > > The code appears

Re: [google-appengine] Re: Issue with Cloud Storage GCS API on local Development Server

2013-12-19 Thread Tom Kaitchuck
Namespaces are a datastore specific concept. It caused trouble in this instance because the local mock of GCS uses the datastore for its metadata. Real GCS does not depend on datastore, so this problem will not occur with deployed code. On Fri, Dec 13, 2013 at 6:05 AM, Troy High wrote: > I was

[google-appengine] Re: Issue with Cloud Storage GCS API on local Development Server

2013-12-17 Thread Troy High
I was having the exact same problem with namespaces and the local dev server not honoring them for some entries. I applied the same workaround as Ken and am able to retrieve files programmatically. So is this a bug in the Dev server implementation or does this mean cloud storage does not offici

[google-appengine] Re: Issue with Cloud Storage GCS API on local Development Server

2013-11-22 Thread ken
> > Nailed the culprit! > We make extensive use of namespaces, and in my original post, there turns > out to be an unfortunate interaction between namespaces and the GCS client > API. > > Down in my original post, where I laid out all the data I could find in > the Development Console, you will