On Mar 3, 7:51 pm, Alex Greif <[EMAIL PROTECTED]> wrote: > > They are different alternatives depending on what you need to do. The > > most basic one to use is WSGIScriptAlias. > > BTW, is this a preferred way for production environment behind an > apache server? (not for google :-)
Do you want to rephrase that, not sure what you are asking? The mod_wsgi module means that your Python application is either running directly in the Apache child process (best performance and scalability), or in daemon processes directly forked from Apache and managed by Apache (best for application isolation and running as distinct users). Daemon mode is sort of similar to fastcgi solutions, but not really, as it is an integrated system where mod_wsgi handles both sides. In fastcgi it is a separate processes created by way of fork/exec and you need separate adapter such as flup where as in mod_wsgi you don't. Also different to mod_proxy solutions where you might run Python web application as standalone process and proxy HTTP requests to it. Out of those four configurations, which are you asking about and what do you want to know? The mod_wsgi doesn't sit behind Apache like mod_proxy solutions do and is also more tightly integrated than fastcgi solutions, thus why am not sure what you asking. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
