In another post someone was exceeding the 5 second timeout with urlfetch trying to get an RSS feed for a Google Docs account. I am planning on using the Google Charts API and I wonder if I won't hit the same issue. However, this got me thinking that writing a service like the Charting API on GAE is quite improbable given what we presently know about CPU thresholds, however we have to presume that the charting API that google offers is scalable. I know the service is new and I don't mind the limits since I haven't actually been locked out yet and I assume things will get better. I would encourage Google to look at the CPU profiles for services like the charting API when thinking about what limits to set on GAE.
On Tue, Sep 23, 2008 at 7:45 PM, Michael Hart <[EMAIL PROTECTED]>wrote: > > Hi all, > > Having been through a number of shared hosting situations, I'm gonna > have to say that I disagree with most of the complaints on this thread. > > I think one of the main things not to lose sight of is the fact that > GAE is intended to be a scalable platform, not a generic hosting > solution. If you want or need a dedicated amount of CPU or memory, > then GAE, at least as it stands today, is probably not what you want. > The limits that are imposed in GAE are there to ensure that your app > will scale. There are many apps that don't need to scale, and I would > suggest that it's probably going to be easier for these to be > developed on a more traditional platform. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
