do I get it? ACL's purpose

After some reading, tinkering, and observing, I think I'm starting
to understand what Cake's ACL is supposed to do and what it isn't. If
you can take issue with any point (or part of any point) below, please
do so and, if you can, give an example as to how it is incorrect. Or,
if you have helpful additions to the lists below, please don't
hesitate to make them known.

Cake's ACL is designed to:
* Create a dynamic (though with some initial setup), logical aro
structure
* Determine what aro's can do to a given type of aco (By type, I
essentially mean class)
* Abstract these permissions determinations from your code so you can
simply ask "can 'x' do 'y' to an aco of type 'z' "

Cake's ACL is NOT designed to:
* Determine what aro's can do to a specific instance of an aco - this
is to be handled by you in your code
* Allow aro's act also as aco's (e.g. a user can edit another user's
info, but not delete the other user)
* Create a user heirarchy (e.g. this employee 'a' is a supervisor of
employees 'b', 'c', and 'd' while employee 'e' supervises employees
'f' and 'g')

Am I pretty close? Way off? (Most likely, somewhere in between?)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---