I'm experimenting with using Perl modules (.pm files) underneath
Mason components.
As far as I can see, the only way to guarantee that changes made in
the .pm are seen by the Mason code is to restart Apache whever the
.pm file changes. This is true whether the "use" statement is in
At 5:30 PM -0800 3/30/01, Randy J. Ray wrote:
I understand the forking model of Apache, and what that means in terms of
data initialized in the start-up phase being ready-to-go in each child
process. But what I need to do is manage it so that a particular value is
shared between all children,
At 12:26 PM -0500 3/12/01, Khachaturov, Vassilii wrote:
When I upgraded from
Solaris Apache/1.3.14 (Unix) mod_perl/1.24_01
to
Solaris Apache/1.3.17 (Unix) mod_perl/1.25
the following code in my debugging httpd.conf broke:
Perl
sub WWW_DIR () { $ENV{'HOME'} . '/www' ; } # this sub will persist
