On 18 September 2010 09:59, Blair McKenzie <[email protected]> wrote: > - the deniedAccess.cfm webskin is used when a user requests a page when they > don't have the View permission or haven't been granted access to the webskin
View permissions are awesome. If you are trying to secure whole areas of functionality then this is the best way to do it. For example, by default anonymous role (ie users who are not authenticated) can see any view prefixed by display* (for example, displayTeaserStandard or displayPageStandard). However, all edit handlers (starting with edit*) and webtop overviews (starting with webtop*) are impossible to view. If you rely on doing a static permission check on every view you are relying on every developer to make sure the check is in place and working as expected. A typical application will be secured with a combination of view security and specific permission checks. You can modify the view permission scheme by editing each specific role. > - it's possible to key webskin caching by the user role Blair says this so casually ;) The entire view caching model is designed to key by role or variable as needed, in addition to all the other great features in its dynamic caching model. Regards, geoff http://www.daemon.com.au/ -- You received this message cos you are subscribed to "farcry-dev" Google group. To post, email: [email protected] To unsubscribe, email: [email protected] For more options: http://groups.google.com/group/farcry-dev -------------------------------- Follow us on Twitter: http://twitter.com/farcry
