Anders, For ajax calls you might consider creating a very simple handler that uses as few modules as possible when performing ajax calls. Then put that as a separate url in your app.yaml. In that case appengine would only load the modules it needs to serve that request and would hopefully not take as long (as say to load a whole framework like django). That might help reduce the latency of some of your ajax calls.
Ian On Mon, Jun 8, 2009 at 3:04 PM, Anders <[email protected]> wrote: > > Ok, just one more comment. Both serious and tongue-in-cheek style. > > To use a metaphor, I hope that Google App Engine will become like a > real car and not be a plastic toy car for kids. Maybe someone from > Microsoft or Amazon has managed to infiltrate the management of App > Engine at Google. Not only do (did) the sometimes exceedingly long > start-up times for application instances suck, there is also (at least > was) a lack of clock synchronization between GAE servers. This means > that an application like Twitter is not possible to implement using > Google App Engine. For example, the Twitter API allows max 50 > something calls per minute in some cases. That's impossible to > implement reliably without predictable clock synchronization between > servers. > > > -- ======================================= 株式会社ビープラウド イアン・ルイス 〒150-0012 東京都渋谷区広尾1-11-2アイオス広尾ビル604 email: [email protected] TEL：03-5795-2707 FAX：03-5795-2708 http://www.beproud.jp/ ======================================= --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
