I was just wondering what people's thoughts were on caching for rules. My thoughts here were that you could either wrap your containers in cache tags with the site skins, or alternatively, add an option to the container/rule management window to setup caching for each rule in a container.
The drawback with applying caching attributes to the container object is the need to look up the object to determine the cache. It's obviously faster to just cache the resulting HTML in the skin.
That being said, caching of the container content on a per container basis has always been part of our original intention.
My motivation for this is to do with the XML feed rule. Currently it hits the source rss for every page view containing the rule. It would be quicker/cheaper for these results to be cached (and the site admin feeding the RSS will get less annoyed).
Have been meaning to re-write that rule for some time :) The rule itself should cache the XML feed and it should maybe keep its last captured feed in case it wakes up and can't reach the source.
I guess at this point in time there are several options: - build caching into the container object code - cache the HTML in the webskin - construct the rule logic itself to provide relevant caching
I think the only reason the container object caching has not been built is that truthfully I don't think we've had a project that wasn't adequately dealt with by other choices. We're pretty client focused and we typically don't add things to core unless at least one client hs found a need for it.
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
