Christina and Jeff, Between both of you guys, I'm reassured, thanks!
This is code that I haven't touched or thought about in a very long time and I've been busy on other things, its been chugging along, slowly but without too many errors for a while now. Over the next few days I'll have a chance to dig in and I'll report back. Thanks, Mike On Aug 25, 8:44 pm, Christina Ilvento <[email protected]> wrote: > Hi Mike, > > We're actively developing the Files API, you may have noticed that we > released a few new additions in the 1.7.1 release like listing files from > Google Cloud Storage and improving the Files API MapReduce input reader. > We're looking into the production issue you filed, please feel free to ping > me directly if you have any other questions. > > Thanks, > Christina > > On Fri, Aug 24, 2012 at 10:57 PM, Jeff Schnitzer <[email protected]>wrote: > > > > > > > > > I don't have any official insight, but the Files API is pretty core to > > appengine - it ties together GAE, Cloud Storage, and the blobstore. > > Google keeps enhancing the Files API, so I would be utterly shocked if > > they deprecated it. It addresses a very concrete need; without it the > > blobstore is almost useless. > > > Google tends to keep APIs in "experimental" phase as long as possible > > (hell, look at the task queue api) even if they are essential tools. > > I wouldn't worry about the Files API going away - although as an > > experimental API, it might change in backwards-incompatible ways. If > > there is something wrong with it, the right thing to do is create an > > issue athttp://code.google.com/p/googleappengine/issues/list. > > > The APIs you have to worry about are 1) the ones that don't get much > > usage, like the Conversion API and 2) the ones that Google hasn't > > figured out how much to charge for yet, like the fulltext Search API. > > #1 may just disappear; #2 may end up with absurd prices (ie, backends > > and ssl). > > > Jeff > > > On Thu, Aug 23, 2012 at 9:25 AM, tempy <[email protected]> wrote: > > > Hi all, > > > > Although I'm not sure if the two are connected, after updating to the > > > 1.7 SDK, blobstore writes using the Files API have become very slow on > > > finalization, frequently failing completely with an IOException when > > > the blobs get to around 2 megabytes. These requests fail after running > > > for 30 seconds. I've filed a production issue here: > > >http://code.google.com/p/googleappengine/issues/detail?id=7992 > > > > I wonder if anyone else has seen such a slowdown. > > > > Also - this leads me to a question about the File API in general. I > > > know Google doesn't comment on feature timing issues, but just in case > > > anyone has any insight... is it a bad idea to rely on the File API? > > > Its been experimental for such a long time that I'm worried that it > > > will eventually be eliminated, just because it hasn't been promoted > > > already. Its also the weakest link in my app - it produces a lot of > > > random errors, more than any other piece of GAE. > > > > If relying on the Files API is a bad idea, how would you guys > > > accomplish the following: I'm using GAE as a sync-backend for a mobile > > > app. The mobile app receives deltas from the GAE app, and these deltas > > > are pre-generated. Generating them on demand could possibly take too > > > long, thus the offline pre-generation. The deltas could be larger than > > > the datastore entity-size limit, which is why I'm storing them as > > > blobs - and then serving them to the app when they're needed. So, if > > > not for the Files API, how would you guys store these deltas? I really > > > hope to avoid the complication of using an additional system that's > > > external to GAE, especially when the blobstore+Files API seem so > > > perfectly suited to the task. > > > > Thanks, > > > Mike > > > > -- > > > You received this message because you are subscribed to the Google > > Groups "Google App Engine" group. > > > To post to this group, send email to [email protected]. > > > To unsubscribe from this group, send email to > > [email protected]. > > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google App Engine" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
