I believe so, it would make sense. But I'd have to ask Matt. On Fri, May 22, 2009 at 10:35 PM, Tomek Kott <[email protected]> wrote:
> I assume that @@cacheStatus has priority over caching settings for a type > using objectbroker? > > And thanks, that makes sense. > > Tomek > > > On Fri, May 22, 2009 at 7:51 AM, Blair McKenzie <[email protected]> wrote: > >> A type will inherit the caching settings of type unless it specifies its >> own. But in general it's better to specify the caching in the webskin >> itself. Saying cache display* just seems a bit hand-wavy, when caching >> should be given a bit more thought like you're doing.l >> >> Caching is done by object, the source of the webskin isn't really an >> issue. As you say, this is controlled by adding @@cacheStatus: -1/1 to >> webskins as appropriate. >> >> Blair >> >> >> On Thu, May 21, 2009 at 11:17 PM, Tomek Kott <[email protected]>wrote: >> >>> Hello, >>> >>> I'm rearranging some things for caching / ease of update purposes in my >>> display settings, and one of the things I am doing is moving to a model that >>> has, in general, one displayPageStandard under /webskin/types/, and a >>> "displayBody" view within that. I know I can clearly cache the displayBody >>> views for each type, but I was wondering about the displayPageStandard (and >>> for that matter, displayHeaderStandard etc.) under the /webskin/types/ >>> folder. It would seem that this would be controlled by >>> /core/packages/types/types.cfc, but since that is an abstract component (in >>> FC terms) I don't know how that would work exactly. Can I still extend >>> types.cfc as usual and just add caching to that? And then if I need to >>> override for a specific displayBody (such as an include) I can just use >>> @@cacheStatus: -1 on that page. Is this right? >>> >>> TIA, >>> >>> Tomek >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry -~----------~----~----~----~------~----~------~--~---
