RE: [PEAR-DEV] [rfc] permissions managment

I don't agree on the names. As many people pointed out Auth is a different thing than Permissions. Think also of the User class thingie ;) -1 on the names and hierarchie. BTW, one auth package is enough. Authentication is just a boolean thing. Is user authenticated or not. After that you use the user class or the perm class. But the auth class just so few things that one is ample enough, imho. I'd go for something like Auth stays as it is Perm Phplib ACL ?? User to define i think that simple and complex aren't good names because it would imply that there are just two perm schemes. What if people want to add their own ? PEAR perms should provide ways to do that easily. As i said earlier the pear command is a good example. Arnaud.