Hi All, Thanks for the replies!
Instead of generating the data and retrieving it on each request, how
> about caching the output of the components? You might want to look at
> HTML::Mason::Request's cache_self().
Oops, I forgot to mention that the data is dynamic and will vary with each
request.
> I think your hunch is also a really good choice. By predefining this as a
>
> > global in the handler.pl, it should be loaded into mod_perl "before"
> each
> > Apache process is forked off. That means the same RAM will be used to
> > provide this data to each separate mod_perl instance, unless + until you
>
> > modify the values in that hash from one of the Perl instances -- at that
> > time, it would be "copy on write" which would make a separate copy of
> the
> > whole data structure in that particular Apache instance (pid).
> >
> > But since you don't plan to change these values ever, you should be fine
> > with the approach you contemplate.
Thanks for the advice, Mark, and also for some insight as to what's going on
under the hood. The global will never be modified/redefined so this sounds
like the way to go. I also looked into Memcached -- very neat. It's
something I'm sure to end up using at some point if not here. Thanks again.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
