Scott - Have you experimented with turning off the trusted cache via the ServiceFactory, or the CFAdmin API?
When the user submits a new page with a cfinclude, you could turn off the trusted cache, hit the page with a CFHTTP to the page you changed, and then turn it back on. (You could do this asyncronously if you really wanted to even, so the user didn't have to wait) Sound too simple? Mark On 7/21/06, Scott Arbeitman <[EMAIL PROTECTED]> wrote: > > 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. > > > > > -- E: [EMAIL PROTECTED] W: www.compoundtheory.com ICQ: 3094740 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
