Hi,
I've got to ask this because I'm going through immense pain and
suffering* dealing with this problem. Why is Apache::PerlRun a subclass
of Apache? Shouldn't it just be a regular content handler that 'has-a'
$r instead of 'is-a' Apache request?
The problem I'm having is that I'm trying to write Apache::Filter as a
subclass of Apache (because it 'is-a' Apache request class, in that it
extends the Apache class), but PerlRun and its derived class RegistryNG
step in and clobber $r.
So I'm trying to open the discussion about whether the current implementation
of Apache::PerlRun might be changeable. I'm about to take a stab at
implementing it the way I think (for the moment) it should be.
-Ken
*Well, perhaps not actual pain and suffering, but I just watched "Buffy
the Vampire Slayer" so it's on my mind. =)
