Hi all,
Can anyone explain to me the differences (pros / cons) between a DSO
and statically linked deployment of MOD Perl?
- performance, maintainability, etc
Thanks for any assistance!
Ben
ben.wilder@gmail.com wrote:
> Hi all,
>
> Can anyone explain to me the differences (pros / cons) between a DSO
> and statically linked deployment of MOD Perl?
>
> - performance, maintainability, etc
>
> Thanks for any assistance!
>
> Ben
>
From README.gz in libapache-asp-perl:
> Linux DSO Distributions
> If you have a linux distribution, like a RedHat Linux server, with an RPM
> style Apache + mod_perl, seriously consider building a static version of the
> httpd server yourself, not DSO. DSO is marked as experimental for mod_perl,
> and often does not work, resulting in "no request object" error messages,
> and other oddities, and are terrible to debug, because of the strange kinds
> of things that can go wrong.
Thanks very much indeed!
Mumia W. wrote:
> ben.wilder@gmail.com wrote:
> > Hi all,
> >
> > Can anyone explain to me the differences (pros / cons) between a DSO
> > and statically linked deployment of MOD Perl?
> >
> > - performance, maintainability, etc
> >
> > Thanks for any assistance!
> >
> > Ben
> >
>
> From README.gz in libapache-asp-perl:
>
> > Linux DSO Distributions
> > If you have a linux distribution, like a RedHat Linux server, with an RPM
> > style Apache + mod_perl, seriously consider building a static version of the
> > httpd server yourself, not DSO. DSO is marked as experimental for mod_perl,
> > and often does not work, resulting in "no request object" error messages,
> > and other oddities, and are terrible to debug, because of the strange kinds
> > of things that can go wrong.