in reply to Re^6: Time to write a "serious" http server in Perl?
in thread Time to write a "serious" http server in Perl?

DSO is better than it used to be in apache 1, so there's less reason to do it now, but I still prefer it because I want control over what modules are loading and specific control over how some things (SSL, mod_perl) are compiled. The default one on distros I've seen includes junk you won't use and forces you to use DSO.

The other big problem is that switching versions of apache will usually break mod_perl, so I can't have the OS swapping it out under my feet. I have to be in control of when apache gets upgraded and to what version, much like controlling your CPAN module versions.

  • Comment on Re^7: Time to write a "serious" http server in Perl?

Replies are listed 'Best First'.
Re^8: Time to write a "serious" http server in Perl?
by autarch (Hermit) on Aug 12, 2008 at 14:55 UTC

    Back when Debian had Apache 1 as the default, it offered a separate apache-perl package that had mod_perl statically compiled. You could install the apache and apache-perl packages together side by side. Very nice.

    Nowadays, with Apache 2, mod_perl is only a DSO, AFAICT, and I needed to set up my own parallel set of dirs, as I mentioned earlier, but it worked fine.

    Since I'm not compiling my own mod_perl2, switching the Apache 2 version isn't an issue, since the packages all get upgraded together.

[reply]

In Section Meditations