There is no reason to think about using CGI at all as many of you noted.
I believe that there is / will be shared webhosting with mod_python / fastcgi support. (At least he can ask admin of LJW, who posted the offer somewhere here :)
To conclude points:
1. don' t use CGI
2. mod_python on shared webhosting requires restart of Apache, when django models change in order to take effect.
3. httpd.conf on shared webhosting is not available (for custom change)
If we deal with #2 and #3 Django can be more adopted.
Radek
On 11/14/05, hugo <[EMAIL PROTECTED]> wrote:
> ( I guess that from this:
>If a Python programmer has a good webhosting ( = share webhosting)
>company, he is happy with, why he should find another one only to
>install Django?)
Because he wouldn't be anymore happy with his webhosting, if he is
forced to run Django under CGI, as that is dead slow. So if his
webhosting doesn't provide either FastCGI, SCGI or mod_python, he would
be forced to find another webhosting anyway, as CGI isn't an option.
The startup time for Django is just to high - and CGI will startup
Django for each and every request!
And even if his webhosting would only provide CGI and he would be happy
with the horrible performance - as soon as the first larger hit on his
app happens, the webhoster would throw him from their host, because
those CGIs will grab much more resources than standard CGIs do.
In short: you really don't want to run any complex web framework from a
CGI environment. Get a decent hosting plan that includes FastCGI, SCGI,
mod_python or user-provided daemons.
bye, Georg
