Well yes, that *could* be done, but I don't think many Apache hosting providers currently do it - most of them simply give each customer site its own virtual host, with appropriate AllowOverrides to allow the customers to control the site through .htaccess files.while this is not an exciting option, if separate per-user processes are needed, there is always apache going via mod_proxy to sub-instances of apache that run for each user's account on different ports, each running mod_python. im not sure how feasable that is to run many servers in various shared environments but I would think most other approaches involve some per-user daemon as well...and i think apache is pretty lightweight if configured so.
Another possibility for shared hosting is chroot jails, but again this is a minority of hosting providers.
[no he didn't, that was me]
Peter Hunt wrote:
Seems to me that mod_python isn't really suitable for a shared-hosting environment because of the need to restart the server when indirectly-imported modules are updated, a situation that I believe mod_python does not detect.
regards Steve -- Steve Holden +1 703 861 4237 +1 800 494 3119 Holden Web LLC http://www.holdenweb.com/ Python Web Programming http://pydish.holdenweb.com/ _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
