Hi AD7six I hadn't thought about using data stored in a session. That would be useful.
I have just used the suggestion in this thread to use requestAction(). I put it in the view rather than in an element and it works fine. The page request time is about half what it would be without caching, so I think that I am getting at least 50% of the benefit of caching. I am going to clean up the appController code a bit which should also improve performance for the requestAction(). I am starting to get a feel for how to use view caching and <cake:nocache>. It really requires (for complex pages) that you plan in the view caching from the start. Regards, Langdon > On Jan 29, 10:33 pm, Langdon Stevenson <[EMAIL PROTECTED]> > wrote: >> Thanks for both of your input. However what I am looking for is a >> definitive answer to the question: >> >> Does the example in the manual work? > > The manual makes no hint as to where $newProducts comes from (that > example?), if it is read/written from/to the cache in your own code, > then yes, otherwise maybe not. > >> I can well understand the difficulties of dynamic data in a cached view. >> However the <cake:nocache> tag was created by someone for a reason. Can >> anyone explain how it is meant to be used? > > In principle, and bearing in mind that no controller code is run for a > cached method (if it was, what's the point?), to read from the > session, or to read data from a cached set of data (I would guess/ > suggest). > > HTH, > > AD7six --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
