Mailing-List: contact modperl-help@apache.org; run by ezmlm
Precedence: bulk
Message-ID: <001f01c0cadd$5f7d3c40$b905a193@jct.ac.il>
From: "Issac Goldstand" <neoi@writeme.com>
To: "Steve Leibel" <stevel@bluetuna.com>
Cc: <modperl@apache.org>
References: <4.3.2.7.1.20010421230215.00b976d0@pop3.netcologne.de>
 <v04210100b707ed6d33bd@[24.168.26.251]>
Subject: Re: Must restart Apache when any .pm changes?
Date: Sun, 22 Apr 2001 05:36:09 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

man Apache::StatINC

  Issac

Internet is a wonderful mechanism for making a fool of
yourself in front of a very large audience.
  --Anonymous
 
Moving the mouse won't get you into trouble...  Clicking it might.
  --Anonymous
 
PGP Key 0xE0FA561B - Fingerprint:
7E18 C018 D623 A57B 7F37 D902 8C84 7675 E0FA 561B

----- Original Message ----- 
From: "Steve Leibel" <stevel@bluetuna.com>
To: <modperl@apache.org>
Sent: Sunday, April 22, 2001 4:14 AM
Subject: Must restart Apache when any .pm changes?


> 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 
> handler.pl or in the component.
> 
> I believe the way this works is that the first time any Apache child 
> process sees "use Foo" that is the version of Foo.pm that will be 
> used by that process.  No subsequent "use Foo" within components will 
> have any effect during the life of that Apache process.
> 
> Am I understanding this correctly?
>