This is the main difference:
DSO:
you need those 2 lines
there's a negligible speed/memory overhead. you'd barely notice it
if you ran some severe benchmarking tests
when mod_perl is updated, you just recompile the mod_perl module
Static:
you don't use those 2 lines
On Tue, 20 Dec 2005, LUKE wrote:
How to setup httpd.conf ? when i using static (non-DSO) mod_perl.
DSO mod_perl httpd.conf ===
LoadModule perl_module modules/mod_perl.so
Don't need that... See httpd -l
PerlRequire "/usr/local/perlmods/startfile.pl"
IF this is mp2, use PerlPostCo
On Tuesday 20 December 2005 01:17 am, LUKE wrote:
> Will i need recomplie apache when i modify my (perl)code , when using
> non-DSO mod_perl?
No. Static mod_perl simply means that the mod_perl module that runs your Perl
code is compiled in as part of Apache itself, rather than being a runtime
ex
How to setup httpd.conf ? when i using static (non-DSO) mod_perl.
DSO mod_perl httpd.conf ===
LoadModule perl_module modules/mod_perl.so
PerlRequire "/usr/local/perlmods/startfile.pl"
Will i need recomplie apache when i modify my (perl)code , when using
non-DSO mod_perl?
