As far as I know that should work. I'll pass the question along to the guy who wrote it.
On Fri, May 29, 2009 at 2:13 AM, Tomek Kott <[email protected]> wrote: > So I tried putting > > <!--- @@cacheStatus: 1 ---> > <!--- @@cacheTimeout: 1400 ---> > <!--- @@cacheByVar: url.year,url.month ---> > > and updating the app, but the caching still doesn't work. Do I need > > <!--- @@cacheStatus: 1 ---> > <!--- @@cacheTimeout: 1400 ---> > <!--- @@cacheByVar: "url.year","url.month" ---> > > or something? Or is there another way to add to the cacheByVar scope? > > Thanks, > > Tomek > > On Wed, May 27, 2009 at 7:42 PM, Blair McKenzie <[email protected]> wrote: > >> You would need to specify url.year, etc. >> >> The caching stuff can only use variables in a scope (e.g. application, >> form). These variables are used to check the cache before the webskin. There >> is no way around that, as the goal is to avoid running the webskin >> unnecessarily. >> >> Blair >> >> >> On Wed, May 27, 2009 at 12:43 PM, Tomek Kott <[email protected]>wrote: >> >>> Hi All, >>> >>> I'm a little confused by the cacheByVar implementation. I am trying to >>> use it on the displayEventsCalendar rule page, and the two variables that I >>> want to hash on are the 'month' and 'year' url variables. so I just did the >>> naive thing >>> >>> <!--- @@cacheByVar: year,month ---> >>> >>> That didn't seem to work by putting in the displayEventsCalendar. At >>> which level of the caching mechanism do I need to put that code in? Does it >>> go in that file (which is a rule display page) or does it go in the dmHTML >>> page that holds it, or the container, or do I need to do url.year and >>> url.month as the variables, for example? >>> >>> Thanks >>> >>> 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 -~----------~----~----~----~------~----~------~--~---
