I do not know much about your application but usually it is not a good
strategy to cache pages or partials accessible only to one user.
Usually these type of pages are not highly traffic-ed (compared to
public pages) and the cache will not be hit so many times (compared to
public pages).
If those pieces take a lot of time to generate I would solve the
caching at a different level (memcache of data).
gabriel
On Jul 1, 4:34 am, Richtermeister <[email protected]> wrote:
> Hi all,
>
> I have an app with 2 usergroups (admins and dealers), and dealers can
> fall into 3 brands. Those two factors affect the content of certain
> lists. Now, I'd like to cache certain sections, but of course I need
> to still worry about who sees what, and I'm thinking that in theory
> this should be as easy as making the two factors part of the cache
> key.
> This way, all combinations of dealer/admin and brands get individual
> caches.
> Is that the right thought, and where would I have to tinker to make
> this happen? I suspect the sfViewCacheManager is a good spot, but I'm
> unsure how exactly.
>
> Thanks,
> Daniel
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" 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/symfony-users?hl=en
