Holger The project I am working on was originally developed under appengine- patch. I ported it to google-app-engine-django when I came across an issue with appengine-patch which took quite some time to resolve. To be fair to the appengine-patch project issue has now been fixed but I would still rather not spend the time porting the application back to appengine-patch again if I can avoid it.
Also, the project I am working on has a very low usage pattern. It is written for my friend's electrical contracting company and there's only 3 of them! This results in zipimport being used a lot and negatively affecting application response times. Since the application is built to be used on mobile browsers and over a mobile data network the response is already pretty slow and adding an extra 1-2 seconds to every second or third page hit really doesn't help! google-app-engine- django allows me to use the build in django 1.0 libraries which removes this workload. (To be fair, the 1.0.2.3 release may have removed the zipimport requirement for django 1.0. I didn't check) Andy On Aug 13, 7:03 pm, Holger <w...@arcor.de> wrote: > Hi Andy, > > you are right, appenginepatch has got a lot of additional features. > > If you don't need them, simply switch them off, as explained in the > manual: > > 'The Media Generator is pre-configured ... You can disable it by > removing "mediautils" from your INSTALLED_APPS. > 'http://code.google.com/p/app-engine-patch/wiki/MediaGenerator > > Holger --~--~---------~--~----~------------~-------~--~----~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
