Khaos :: KhACL

[eluser]Neophyte[/eluser]
personally i think my approach is more logical but i would say that but basically i think my approach is more true to how each of the ARO, ACO and AXO objects should work respectively.

The phpgacl approach would polute the ACO table with both control objects and action objects and means duplicating control objects which already exist into the AXO table (just look at their table schema)

Consider a news article and a user where you want to make it so the user needs permission to publish.

My approach means you would create the ARO (user), ACO (news article) and create the Publish action (AXO) and then create the relationship between them all $this->khacl->allow('user', 'article', 'publish'); to check if a user has access to the news article you just check the ARO against the ACO, if you need to check the user has publish rights you additionally specify the AXO.

With the phpgacl approach you would create the ARO (user), ACO (news article), publish action (ACO) and then AXO (news article again) then establish the relationships between them. To check if a user has access you check the ARO against the ACO. to check if the user has publish rights you check the ARO against the AXO (which is now acting as the ACO) and put the action as the actual ACO.