I'm using Apache::Session within a large Web application (consisting of many
scripts). We also have multiple developers on this project, some of whom
are junior developers with only a bit of mod_perl experience.
In any case, I've written a custom session package that wraps to
Apache::Session.
You could try using a PerlCleanupHandler to kill any open locks.
$r-register_cleanup( \clear_locks );
- Perrin
Perrin,
Thanks a lot. This worked great :-). Actually, as I say, I'm wrapping to
Apache::Session with another object that handles cookies, expiration, etc.
I just registered a
MR Wrote:
My site is starting to get "busy enough". Are there some docs that
explain how to to do this. Apache proxy has always seemed unclear to me,
my lack of understanding really I've been using standard apache with
mod_perl for several years now and have run squid in front of it, but
Hey guys,
Before I start with my problem / question, let me just say that I haven't
been subscribed for a while. I was doing some heavy mod_perl development
last year, and I was subscribed to the list for a long time. Eventually,
mail from this list and the other lists I was subscribed to got
Thanks James,
Great little trick It worked!
Thanks for the help,
Russ
Russell Weiss
Founder and Technical Manager
InfoRelay Online Systems, Inc.
http://www.InfoRelay.net/
Try
bless $self, $class;
$main::SIG{'__DIE__'} = sub { $self-custom_die(@_) };
This will make sure
It seems as this has the effect that each server process keeps its own
copy of the templates. I would like to avoid this by using some sort of
shared memory between the server processes. Does any of you have any
experience in this field (or even better examples of how to do it)?
A good
Hey guys,
This relates somewhat to the message that I sent last night / early this
morning.
I have a custom $SIG{__DIE__} handler defined within an object. Upon a die,
this handler runs the object's DESTROY method. As I stated in my earlier
message, I'm doing this because the object contains
