On Wed, 26 Mar 2003, Chris Leishman wrote: > I'm also curious - it seems that the implementation of XSP.pm attempts > to cache the result of the XSP processing (the output from the > generated perl module). Yet I thought that the results couldn't be > cached/shouldn't be cached, since they are dynamic.
That was just a dirty rumour ;-) If you implement a has_changed() method on your page, it overrides the default implementation that returns true always, and you can return false under some given condition, thus AxKit uses the XSP output cache. > Also, why isn't > the compiled XSP (the perl module) written to a cache file? Currently > it's only cached in memory. I never saw the point. Compiling XSP pages is very quick... I think I left it that way to motivate myself into writing the pre-fork compilation of XSP pages, which would mean they never have to be re-parsed unless they changed. This way they get re-parsed every time MaxRequestsPerChild is reached, but I don't consider that too much of a headache. But we've argued the toss on this one before until I yelled "Patches welcome!". I still havent had chance to look at your patches. Day job getting in the way. Hopefully before another fortnight disappears I'll get through it. Matt. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
