Possible answers: 1) Many people like the convenience of one process to watch, i.e. the main apache process [that monitors its own child processes]. Using SCGI means you have externals processes to watch in addition to apache. Though if you use a multi-apache setup for lightweight and modpython apaches you have mulitple processes anyhow -- but many people are more familiar with supporting good ol' 'httpd' as opposed to standalone python processes.
2) People are already running other apps/sites largely dependent on apache. Most of the Rails folk looked to lighttpd (and similar) because Apache1/2 FastCGI support is apparently quite flakey, with mysterious zombie processes and so on. Lighttpd offers better FCGI support so that was a common solution. Now that Mongrel exists (a standalone HTTP-talking ruby/C server), people are migrating back to Apache (2.2.x) to take advantage of its mod_proxy support for load-balancing -- to distribute load to multiple Mongrel procs on the same or different servers. Also modruby (if still in existence) is not often used, so that whole option (equiv of modpython/modperl) is not there; Mongrel is [very] roughly the equivalent of modpy/perl (without the apache part of course). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss -~----------~----~----~----~------~----~------~--~---
