Tree permissions are extremely complex, for both navigation and content. If that is what you're trying to filter by, then what you were doing originally is as simple as it gets. Perhaps some optimisations where out-of-tree objects are checked as I described.
Keep in mind that the permission should mean that checking a permission for an object should should be very quick after the first time. 'View' in particular should always be cached since that is checked during normal browsing. On Thu, Jun 18, 2009 at 2:09 AM, Might Aswell <[email protected]> wrote: > > On Jun 16, 5:15 pm, Blair McKenzie <[email protected]> wrote: > > Keep in mind that this wouldn't be enough for dmNavigation - > > in that case you would also need to check for barnaclevalue = 0 and do > the > > checkPermission call for those. > > Blair, > > Not quite sure I understand "this wouldn't be enough for > dmNavigation". Would this apply only if I have a dmNavigation > collection? Or are you saying the direct query example you provided > will not check the view permission on a dmHTML under a protected > dmNavigation (the problem i am trying to overcome with results)? > > I think a nice feature request for farcryVerity would be to by > default, filter protected content from the results. Also, the ability > to assign perissions to "collections" would make it much mroe usable. > > Chris > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
