On Fri, Apr 16, 2010 at 10:46 AM, Carlo Trimarchi <mr.spoo...@gmail.com>wrote:
> On 16 April 2010 14:42, Karen Tracey <kmtra...@gmail.com> wrote: > > Why are you trying to use mod_python here instead of mod_wsgi? mod_wsgi > is a > > lot easier to configure properly for this type of setup. > > Not sure. I thought it was the preferred way, byt maybe I'm wrong. Is > there any advantage in using one instead of the other? > mod_python development is moribund, mod_wsgi has an active helpful maintainer. It's reasonably straightforward to configure mod_wsgi to get control only for a certain portion of the URL space, getting that config correct for mod_python/Django is not so straightforward. You can also configure mod_wsgi to operate in daemon mode, so that all of the mod_wsgi/Django request handling is done in independent processes distinct from the normal Apache child processes, which can help immeasurably in eliminating conflicts in libraries, etc. between PHP, Python and whatever else is running in Apache. Karen -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
