On Mon, Jan 16, 2012 at 11:12 PM, Stuart Laughlin <stu...@bistrotech.net> wrote: > I also note that everyone who advocates > for apache concedes that the default installation/configuration is really > not appropriate for django apps. I intend to look more deeply into the > suitability of the default configurations of nginx / lighttpd / cherokee as > delivered by various linux distros. Finally, your point about mod_wsgi's > superior configurability is a good one, and something I had not considered.
You're inventing words that you think I said. The 'default' config is entirely appropriate for django apps, it is however not high performance. I say 'default', because it is only the default on certain OS. On the platform we serve on, FreeBSD, it is a simple choice which MPM to choose, and the default configuration for Apache configured with worker or event MPM is entirely on par with nginx/lighty. On top of that, you get all the advantages of being part of the Apache ecosystem. Apache 2.4.0 will be released this week (probably), with a mass of enhancements: http://httpd.apache.org/docs/trunk/new_features_2_4.html I'd thoroughly recommend not ignoring Apache in search of the new cool. Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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.
