It is always better to run frameworks by themselves and just have a small hook *.wsgi script to connect you to the framework. I'm surprised there isn't some sort of hook script already with cherrypy, I know Django has one and many other have one also.
Graham correct me if I'm wrong, but mod_wsgi imports all the *pyc files that the hook script calls, so subsequent requests will all be much faster anyway, but I still wouldn't advise depending on this with a large framework. -Carl On Wed, Oct 22, 2008 at 1:46 PM, roberto <[EMAIL PROTECTED]> wrote: > > hi all, > > hopefully not a question answered here, i couldn't find anything > relevant in my searches. otherwise i do apologize. > > i have an http python application that has some relevant processing > power on start up. for this reason, instead of having apache with > mod_wsgi launching my application on every http request, i have > integrated cherrypy with mod_wsgi. > > my question is: would i be better off using cherrypy directly [and > apache only for proxying]? or is this the best way to go? i am > expecting consistent load and trying to maximize answered simultaneous > connections. > > thank you, > > r. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
