On Sat, 23 Mar 2002, Andreas J. Koenig wrote: > [bounced to list with permission] > > Hi Barrie, > > thanks for your article > http://www.perl.com/pub/a/2002/03/12/axkit.html, it's a great help to > me to get an overview. I'm interested in AxKit since it exists but > always missed the starter kit. I hope to come around to use it in a > future project. > > But one thing is there in your article that is probably misleading: > > Note that AxKit is smart enough to not cache the output document > (there's no cache between the XSP processor and the output); XSP is > intended for dynamic pages and its output documents should not be > cached. > > I do not believe that dynamic pages should not be cached, it's all a > matter of expiration times. Even dynamic pages can have a long > expiration time and should be cached if the cost of caching is lower > than the cost of recalculating.
I agree. The redesign of AxKit (AxKitNG, AxKitB2B, or whatever we decide to call it) is taking on these concerns. I think basically caching in AxKit 1.x is too automated. For the re-write it will be a part of the processing pipeline, and will be applyable to any and all sub-parts of the pipeline. The cache will be based on XML::Filter::Cache, which supports pluggable storage mechanisms, and you will be able to define your own cache-config system, where you get to choose whether to deliver the cached copy or not (with some defaults provided based on mtime and ttl). Of course work hasn't really even begun yet on that, because I personally don't have a huge itch to scratch with it - I'm just curious to get it done to see if it really is better. Perhaps we'll have a hackathon at TPC this year to convert AxKit to this new model and see if we can't make it work. -- <!-- Matt --> <:->Get a smart net</:-> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
