On 26 Oct 2005, at 13:33, Ken Neighbors wrote:
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.)
For the next version of AxKit (not 1.7, which I'm ready to release now once I remember how to do apache's release procedures) I'll be implementing XSP caching "properly" end to end.
Currently you can cache the output of the XSP (i.e. the XML that the XSP produces) but it will still run the rest of the phases after that, which is bad. In order to fix that I need to have the cache dependency checking code call into the XSP page (assuming it has been compiled) to check if we have a cached page. That adds a bit of complexity to the dependency checking, but it's the right thing to do.
Matt. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
