coplet caching for individual users versus whole site [additional keywords: authorisation, authorization, portal]

[Surjan Singh <su...@misgl.com>]

Hello,

Can anyone help me understand how coplets are cached for different users 
in the portal?

We have a requirement where certain types of coplets need to be cached 
site-wide (regardless of the logged in user), whereas other coplets need 
to be cached per-user.

For example, a coplet that shows the status of a system will be the same 
for everyone, but one that allows a user to change their account details 
will need to be handled per-user.

Any help / tips / pointers appreciated.

Thanks,
Surj

[additional keywords: authorisation, authorization, portal]

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org