> If it is to bring down application for maintenance, seems like it > would be easier to use Apache/mod_wsgi in daemon mode.
I'll give mod_wsgi a go. To be honest I never looked at it before simply because it is tied to apache. But if it can easily do everything I need using a reasonable amount of memory and provide decent performance, then I'll allow it ;) My app pre-dates mod_wsgi and at the time mod_python just seemed too bloated. I've never been an apache fan and memory usage is/was my main concern which is why I leaned towards lighttpd. At the time I felt that it performed better with serving up static files, but I haven't actually benchmarked it in ages. I suppose you can run lighttpd/nginx in front of apache, but all apache is really doing by then is act as a proxy that converts http into something mod_wsgi daemons understand which just feels terribly bloated to me.. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
