Matt Sergeant writes: > 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.
Sounds great! > 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. For my workaround to get XSP caching to work end-to-end I took the opposite approach: I made my XSP page call AxKit::add_depends to add files to AxKit's cache dependency checking, so that AxKit would handle the details for me (instead of me having to write a has_changed method in the XSP, which, as you say, would only have cached the XML that XSP produces and not the final PDF). Read more about it here: http://www.nsds.com/software/perl/lib/Apache/AxKit/Language/XSPcaching.html If anyone is interested you can download it here: http://www.nsds.com/software/ Ken --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
