Yikes, more than 1000 files sounds pretty big. At least for a template engine. Maybe Django is capable of a lot of stuff. I only use a few very simple template statements. It would be fairly easy for me to replace Django with some manual much more lightweight code, but on the other hand, the Django performance is fast when my application is loaded, and I still doubt that Django has much to do with the long delays during cold starts. The same with JSP. And why would Django, or code for rendering JSP, need to be loaded every time for each application? Let's say that one server has 100 applications loaded using Django. Does this mean that the same Django (large) code is duplicated 100 times in the server?!
On Feb 23, 1:02 am, Wooble <[email protected]> wrote: > On Feb 22, 12:42 pm, Anders <[email protected]> wrote: > > > And that Django can cause several seconds of extra delay doesn't sound > > plausible. > > In the early days of App Engine, there were complaints that django > couldn't be used because of the 1000 file limit. This is pretty much > the definition of a bloated framework. -- 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.
