On 1/25/07, Mihai Preda <[EMAIL PROTECTED]> wrote: > I'd like to know why is that. Does mod_python offer some advantages, > and which ones?
My personal two cents on the matter: Apache is the most popular web server in common use, and mod_python is mature, well-understood and able to work with Django "out of the box". FastCGI under Apache, on the other hand, has two competing implementations -- mod_fastcgi and mod_fcgid -- and can't talk directly to Django or most other Python applications; you have to go get flup and let it translate between FastCGI when talking to Apache and WSGI when talking to Django. FastCGI also introduces a bit more complexity into the setup; with mod_python, your Django application processes are Apache processes, and vice-versa, so Apache's standard process controls (MaxClients and friends) are all you need to control Django. FastCGI spawns long-lived external processes and requires two sets of configuration directives: one for Apache's own processes and one for the FastCGI processes. Depending on the setup, you may also need a separate initialization script to launch the FastCGI processes after a server reboot. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
