> 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.
Thanks for the response Geoff In all honesty, I couldn't really think of any other circumstances where caching was all that vital in containers apart from the XML feed publishing, so I agree with you in that the caching should be handled at the rule level for this. For arguments sake, if the XML feed rule were used elsewhere apart from containers (ok, this is the only place rules are used in FarCry, but anyway...) then caching would still be possible needed for XML publishing, hence it should be handled in the XML rule as opposed to being a function of containers. Having said that, it's a nice little rule anyway, very funky Cheers -- Quentin Zervaas Web Developer MITOUSA. Web + Interface Architects E:// [EMAIL PROTECTED] W:// www.mitousa.com --- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
