Quote:
Originally Posted by u-Bob
true, but let's not blame the language for the faulty implementation  |
Too bad grouchy doesn't know that mod_perl is installed by the host and not
needed in my perl script. It's like php used to be in the cgi-bin and
with "mod_php" it's part of apache. Same with mod_perl.
He thinks I'm going to write mod_perl into my tube script!!
That would be great for servers that don't even install mod_perl.
mod_perl is not a programming language; it's configuring the PERL interpreter to run as part of apache.
This is done by the hosting company, not me.
http://perl.apache.org/start/index.html
Quote:
|
The standard Apache::Registry module can provide 100x speedups for your existing CGI scripts and reduce the load on your server at the same time. A few changes to the web server's config is all that is required to run your existing CGI scripts at lightning speed.
|
The reality here is tubecgi works absolutely great and I'm running five tubes
on one shared account with my regular host.
I just don't want to deal with all the mis-information that people think is fact anymore.
So if noone uses my script, I don't have to deal with it. Hence this post.
These two links explain it all :
http://en.wikipedia.org/wiki/Mod_perl
http://www.revsys.com/writings/modperl.html
If a host does not want to install mod_perl just like they install "mod_php" then is it
really my fault?
I've got something totaly differrent in the works and tubecgi is not where I even want to
spend my time now.
So, it's a blesssing to have people stop using it, even though they can.