perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Wilder" <>
Subject RE: Reloading .so files and .pm files
Date Tue, 05 Sep 2006 08:11:54 GMT
Hi Philip, 

Just a note to thank you for taking the time to put together an example.
It's very much appreciated, and has taught me a fair bit. Your comments,
examples and suggestions have enabled me to create a working prototype. 

I have a few long evenings with the Mod_perl docs I believe! :)



-----Original Message-----
From: Philip M. Gollucci [] 
Sent: 04 September 2006 10:01
Subject: Re: Reloading .so files and .pm files

Ben Wilder wrote:
> 1) Your handler example is fantastic, however in my application I need to
> set the $pkg (the package to be dynamically included) from some logic in
> another script, so the process may go as follows: 
> User request -> main script -> database call to get $pkg name - >
> dynamically call the package (as per your example).
See attached,, and httpd.conf which will runs under the
handler (handlers are better though :)).  The functionality is now in a
library and can be called
from anywhere.

Your variables need to be scoped to a FUNCTION via
'my' (or re-initialized properly on each request) This scoping is the
solution to your caching problem.

You need to read up on the "Core" modperl principles and what it actually
does with your code and how it caches it.
While for 1.x the same principles apply to 2.x

> If my thinking is correct (and I'm a little new to Mod_perl!) the handler
> example you kindly wrote will be called when the /foo path is visited,
> however I will be needing to deliver this from a number of places (and
> not be able to rely on paths in the url) and would IDEALLY call the
> functionality from within a script, rather than having it as a handler. Is
> there a way to do this and still not have the cache problem?
Thats correct, and see the attachments.

> 2) What is the best way to install the libapreq objects, can the same
> functionality be got through the Apache2 classes?
download the lastest 2.08 un zip/tar and read the INSTALL file.
Apache2::* classes are wrapper around the APR::* classes (similar but not
always directly equivalent)

In general though both can get you what you want.
(attachments use Apache2::Request instead of APR::Request::Apache2)


Philip M. Gollucci ( 323.219.4708
Consultant /
Senior Software Engineer - TicketMaster -
1024D/A79997FA F357 0FDD 2301 6296 690F  6A47 D55A 7172 A799 97F

"In all that I've done wrong I know I must have done something right to
deserve a hug every morning and butterfly kisses at night."
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /
 / /|_/ / // /\ \/ /_/ / /__
/_/  /_/\_, /___/\___\_\___/

View raw message