For example, you would probably do better in the long run using the mod_perl
Apache module instead of processing your Perl-powered pages through CGI. When you
call a script from Apache, the Perl interpreter process starts, does its work, and then eventually
stops. You can just imagine what that does to your system??™s resources if you have
20 scripts running simultaneously, even if just for a few seconds. When you channel
those scripts through a module, everything is handled by one native interpreter. This
makes everything go faster??”and safer.
The downside is that mod_perl is much fussier about errors. Apache doesn??™t really mind if
you don??™t release a resource programmatically, because it shuts down the script before that
becomes a problem. In a module, errors accumulate and become real problems. The upside
is that you will become a better programmer as a result of fixing all these problems.
Some languages are specifically designed to be run through an Apache module, such as
PHP. PHP can be used to process scripts through CGI; the language??™s documentation
encourages the use of an Apache module over the CGI implementation.
Pages:
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052