Tom Kirkpatrick writes:
> I attempt to turn off cache by $r->no_cache(1); - This does not seem
> to work... Is this being overriden later on by some AxKit internals
> I am not aware of? Is it even possible to turn off cache from within
> a plugin?
I glanced at AxKit.pm and Apache/AxKit/Cache.pm and it looks like
plugins are run before the cache object is created. But when the
cache object is created it does not look at $r->no_cache() but only at
$AxKit::Cfg->NoCache() as you can see:
if ($AxKit::Cfg->NoCache()) {
$no_cache = 1;
}
I see two possibilities:
1) In your plugin use the following hack in addition to $r->no_cache(1):
$AxKit::Cfg->{cfg}{NoCache} = 1;
2) Patch Apache/AxKit/Cache.pm and change the lines shown above to:
if ($r->no_cache() or $AxKit::Cfg->NoCache()) {
$no_cache = 1;
}
I don't like either method, but I didn't see anything better. Perhaps
someone else has an idea.
By the way, I'm curious, what method are you using to generate the
content on the fly? I'm using XSP and the problem I'm working around
is that it always turns *off* AxKit's caching for the final output
(PDF in my case) even when I say $r->no_cache( 0 ). I've worked
around this problem by subclassing Language/XSP.pm to keep the cache
enabled. (If anyone needs this feature, let me know.)
Ken Neighbors
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
