We have "content" people who are always editing pages which are included via CFINCLUDE. We don't want to require them to know anything about trusted cache, i.e. "when you change content, turn off trusted cache, go to the url of that content, and then turn trusted cache back on".
I've explored other options, such as using JSP includes for this kind of content, because that bypassed the trusted cache. But this is an old system, and there are hundreds of such cfincludes. I've also written a trustedcache tag, where the trusted cache is enabled in between the start and end tags, e.g. <cf_trustedcache> ... lots of CFCs are created here... </cf_trustedcache> The problem here is that trusted cache is always set per server, and if code in between tags is executed often, the cache may never really be turned off, cause all sorts of problems. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfaussie -~----------~----~----~----~------~----~------~--~---
