On Fri, Apr 16, 2010 at 3:46 PM, 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 - python interpreter in every apache child, high memory usage, hard to configure mod_php - php interpreter in every apache child, high memory usage mod_wsgi - out of process python interpreter, communicates with apache using lightweight IPC, low memory usage, easy to configure, only supports python* mod_fcgid - out of process interpreter, communicates with apache using lightweight IPC, low memory usage, easy to configure, supports all languages (not just python) Choice is yours ;) Cheers Tom * well, it supports 'wsgi' protocol - only python talks wsgi 'natively'. -- 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.
