Re: Another Auth-class

> I did not mean to be rude or anything so you don't have to flame me... I didn't want to flame anybody. But it seems to be, that you missunderstood that some parts you are planning is app dependent and can't cover be PEAR. +----------------------------------------+ | Application | +----------------------------------------+ /|\ /|\ | | \|/ \|/ +---------+ +-------+ +--------+ | User | | | | User | | Admin |<--->| User |<------>| Auth | +---------+ +-------+ +--------+ /|\ | \|/ +----------+ | Data | |container | +----------+ User-Admin: create, delete, edit a User-object User: encapsulate the specific userdata in the datacontainer User-Auth: all functions which related to login, acl User-Admin and User are app spezific, i never know what a 'user' is, and you can't administrat anything unknow. For the User-Auth you need only a user id and perhaps the password for auth, this requirements are matched in every case of a user specific app. So this part is the only thing which should go into PEAR. I really recommend you to take a look of the user class in PHPLib, then you can understand what is nec for a User-Auth