On 1/29/07, Kaste <[EMAIL PROTECTED]> wrote: > > > this might work, but, again, cake would access/render/insert 10 > elements/files just because of the usual logged-in-user-area. # >
I know I sound like a broken record here, but you can't have it both ways. You can't have an entire view cached if you have any dynamic content in it. I think to do the type of caching you require, which is to have some dynamic content mixed in with cached content, you will require custom caching functionality beyond what Cake (at least through my limited experience with it's built-in caching) current offers. Which is why I suggested elements. If you can cache elements, then the load is much less and if you have intelligent cache updates mixed into your controllers, you'll get maximum caching benefits. Caching user-specific data is always tricky, but I imagine something like caching the login/logout stuff you're talking about would be dead simple...provided you use a key based on the current session or current user. Trust me on this one, because I have dealt with caching issues on a site that got more than a million hits a day, that used a mix of static caching and dnyamic data. Not a Cake site mind you. -- Chris Hartjes My motto for 2007: "Just build it, damnit!" rallyhat.com - digitial photo scavenger hunt @TheBallpark - http://www.littlehart.net/attheballpark @TheKeyboard - http://www.littlehart.net/atthekeyboard --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
