The major problem is that only one request may be served at a time. Also, the server code has not been thoroughly audited for security flaws--another major problem. I've heard reports of people using MPM Worker just fine with Django, even though it's not officially supported. I'd recomment trying to use mod_wsgi[1] if possible as it's quite simple to set up[2] and it works arguably faster than mod_python in a similar setup.
Hope that helps, Eric Florenzano [1] http://code.google.com/p/modwsgi/ [2] http://code.google.com/p/modwsgi/wiki/IntegrationWithDjango On Jan 13, 2:02 pm, Florian Lindner <[EMAIL PROTECTED]> wrote: > Hello, > what is your opinion about the following deployment configuration? The > site is very low traffic. > > Let the django development server bound to localhost serve the pages > and use mod_proxy from Apache as a front end. > > For me it has the advantages that it fits much better into my setup > than mod_python. Additionally I don't use MPM prefork which according > to the docs is recommended for mod_python. > > Will this be working or are there any major problems? I now it's not > the optimal solution.., > > Thanks, > > Florian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
