RE: [PEAR-DEV] Another Auth-class

> 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. <snip> > 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 I will have a look at it ;) I agree that is is difficult to know what a "user" will be and that it is very app dependent. However, isn't there a way to provide standard methods for managing users ? app dependent would just be extended from them. To take what Luc wrote "So the point was : as a lot (perhaps 70 or 80% ) of what is required to manage users, is staadard from an applciation to another, what about creating a common base for that allowing several php packages to share the same user management basis (extended on a case by case basis to fulfill 100% of the application needs)." Is it completely hopeless ? Arnaud.