On Dec 18, 5:10 pm, Thomas Johansson <[email protected]> wrote: > I just want to address one thing here: There is nothing in AppEngine > that is tied in any way to django or any framework. They just expose a > ...
Sure, of course. By API I loosely included the supplied default appengine frameworks. I suspect there aren't many AppEngine users that are building apps without using webapp or django right now. If I'm wrong then carry on, I retract everything. >... complexities of getting it > working on your own with the current 1000 file and 1mb size > limitations... That's the easiest part, and most appengine django users are doing just that (simply by omitting seldom used parts of django). The cost of repeated zipimports on requests is the problem. It eats into your quota. Unless I'm not understanding how appengine works, I would assume that if django 1.0 was included with the default frameworks there would be a high likelihood that it is always in memory. I'm using Django 1.0 now on appengine without any other issues besides that. CPU quotas are really tight right now, so it makes sense to minimize expensive events. That's all I'm sayin' > On Dec 19, 1:54 am, cz <[email protected]> wrote: >... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
