Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (asf.osuosl.org: local policy)
From: John Doe <security.department@tele2.ch>
To: modperl@perl.apache.org
Subject: Re: mod_perl: How pass variables (objects) from page to page?
Date: Tue, 15 Nov 2005 10:33:03 +0100
User-Agent: KMail/1.8.1
References: <2005111419115.287860@kindness> <dlc1e7$ih3$1@sea.gmane.org>
In-Reply-To: <dlc1e7$ih3$1@sea.gmane.org>
MIME-Version: 1.0
Content-Disposition: inline
Message-Id: <200511151033.03281.security.department@tele2.ch>
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Jeremy Nixon am Dienstag, 15. November 2005 08.06:
> Peter1 Alvin  <temp1@awebabove.com> wrote:
> > Please tell me I can do this!
> >
> > Using mod_perl, how do you keep Perl objects in RAM from page to page?
[...]
> As an example, I have a handler that needs to read a directory listing.
> Most of the time it will be looking at the same directory over and over,
> so I decide that it's okay to have to restart the server if the listing
> will change (the listing won't change much) and do something like:
>
> { # start a lexical scope
> my %d_cache;
> sub handler {
>     # stuff
>     if (not defined($d_cache{$foo})) {
>         # pull in directory listing and store it in $d_cache{$foo}
>     }
>     # proceed to use $d_cache{$foo} information
> }
> } end lexical scope
>
> This way, a directory is only actually read once (at most) per server
> child process.

Hi Jeremy

Hope it's not a stupid question, but are you sure %d_cache survives a request? 
Maybe I'm totally misunderstanding something but I thought after the point 

} end lexical scope

%d_cache gets destroyed (if not still referenced from somewhere else).

I would have left out the scope-{} to keep %d_cache at file level.
Would that be wrong? And why?

I'd appreciate every hint.

joe