On 8/24/07, Cliff Hirsch <[EMAIL PROTECTED]> wrote: > > As for phpGACL, the feedback I got was that most ACLs out there are > > good at answering one question, from the following list: > > > > 1) "Can I access this object?" > > 2) "Who can access this object?" > > > > The trouble is finding an ACL that is equally adept at doing both. > > I understand #1. That's the main point -- access control. But why do I need > #2? To see if I need to bar the door for someone as the # of rules, groups, > users grows increasingly complex?
I think number 2 translates to things like "Who else can read posts to this forum?" or "What developers have commit access" or even reports like "List all editors by site". -- Chris Snyder http://chxo.com/ _______________________________________________ New York PHP Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
