On Apr 25, 9:47 am, Don Spaulding <[EMAIL PROTECTED]> wrote: > On Apr 24, 6:34 am, Rufman <[EMAIL PROTECTED]> wrote: > > > Hey Graham > > > thanks for the insight > > > Stephane > > I won't debate any of what Graham has said, as it's a pretty standard > answer from what I've seen, and he's a lot smarter than me. I just > want to note that fastcgi makes a nice separation between app and web > server for my needs. I hated having to restart apache to restart my > app, and fastcgi on lighttpd made app deployment stupidly easy (not > that apache/mod_python is rocket science).
When you use mod_wsgi daemon mode, to restart your Python web application, which can potentially be running across multiple processes, you just need to touch (ie. update its modification time) the WSGI script file which is its entry point and process will be restarted automatically the next time a requests arrives for them. In other words, with mod_wsgi daemon mode you do not have to restart the whole of Apache when you change the code just for your Python web application. Thus, just as stupidly easy as some fast fastcgi implementations/configurations. :-) Graham --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
