Hi Dan, Ruben,
Actually I once build a commercial Enterprise CMS where a custom content
proxy would cache everything. It was flushed on time-out /and/ upon
changes in the content. The proxy allowed large companies to set up
caches wherever they pleased and still have a central repository. The
caching was fairly complicated as we had a broad definition of what
constituted as a change. The most difficult part is pages that contain
generated stuff that uses the structure of the content tree, like menus.
So my question to you is: how do you flush pages with menus that are
generated from the content tree?
Regards,
Erik.
Ruben D. Orduz wrote:
> Just as an anecdote, I've worked with paid enterprise-grade CMS's,
> open-source CMS's and I've only seen two types of caching:
>
> 1) The classic: time expiry unless forced by hand.
> 2) Tag-level caching: You can choose which tags NOT to cache. So for
> example, in a news site, pretty much the whole site could be cached,
> except for content produced by <%breaking-news%>.
>
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
_______________________________________________
Radiant mailing list
Post: Radiant@lists.radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
