Re: Auth_Groups and Auth_Permissions

On 15 août 04, at 06:04, Jon Wood wrote:

snip

By allowing the grouping of users, and checking permissions. Auth doesn't allow this at the moment without custom writing the same code that everybody else has written 10 times before. These packages are intended to provide a simple solution to that problem.

you are talking about the other draft, I was talking about Auth_Permissions.

Auth might not cover it all but LiveUser does cover a more complex structuring of an authentication system. Your current possible api (e.g. Checks if a user has access. Sets $user to the default access for $permission.) is already covered. I don't see anything new. Using different functions or removing some functionality in the existing packages to make a lightweight version is not sufficient in my opinion.

Can you please point out *where* it is covered - LiveUser doesn't count, since it's virtually undocumented,

what do you mean ? They do have a wiki (http://pear.limbourg.com/) and a number of tutorials. The not completely documented is not a good idea to start a new package.

too much hassle to get working, and tries to do everything.

I can't comment on the "too much hassle" this is a subjective statement as the second. So, do you think that if I think that DB is not good enough because tries to work with too many database (and perhaps to do everything) I could propose (and provide something valuable to PEAR users) another mini abstraction layer ?

I'm aware that this may not seem like a huge, earth-shattering package, but it was never intended to be - it's meant to be a small, light, package, which does one job well. I believe that is the description of what a PEAR package should be in the manual. I never said that a package has to be huge or earth shattering to be interesting.

I just don't see the benefit of it in the Auth branch, Feel free to move on with a proposal if you wish to do so. At a draft level you are asking for comments and suggestions and I did my best to provide some comments (and is not easy at a draft and pre-code level). Regards David Costa