On Feb 4, 8:20 pm, "TT" <[EMAIL PROTECTED]> wrote:
> One of the nice features of Cake, is that it offers View-caching. At
> least, that's what I thought, untill I really wanted to use it. It
> turns out your controllers are completely bypassed when you use Cake's
> builtin cache. This has the effect you cannot use any helpers etc that
> are set from your controllers. BIG problem. Why?
Yup, it's a pretty big problem if you don't know how to use it
properly.
> Suppose you have a site that requires your users to login. Now you
> save your users in a session, but you build a nice component and
> helper for it to access them. Now it turns out you cannot display the
> current user on the cached page anymore because you cannot access the
> helpers. Or for example you want to protect access to some pages.
> Impossible when you want to use caching.
So you're going to try to cache full pages with user-specific data...
yeah, that'll scale *real* well...
> It seems to me that Cake's caching was only build with websites in
> mind that don't allow/require users to login.
Again, the trick is knowing how to use it.
> I think this is a BIG
> problem for many web2.0 sites. Any plans to change this in Cake 1.2?
Hopefully you'll realize how well your suggestion won't work once you
start to think through it. However, if you'd like to suggest a
specific approach, and/or have a working proof-of-concept, we're all
ears.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
