Re: [naming] permissions managment

On Mittwoch, 14. August 2002 11:32, Lukas Smith wrote: > > > Does this mean we all agree to put this user class into the Auth > > > category ? > > > > This is a tricky one. > > > > What the class can do is: > > - User management (add/edit/delete users) > > - Authorization (user login management) > > - Permission/ACL management > > > > So the possibilities I see are: > > - User_LiveUser > > - Auth_LiveUser > > - Perm_LiveUser Auth_LiveUser -1 I don't see the point why there should be one more package for user authentication. The current Auth package does all the necessary stuff. There are some good ideas in Markus' LoginManager class which I would like to see in the current Auth package - but there's no need to start a new one. User_LiveUser -1 Furthermore, I have my doubts if it makes sense to have any kind of User_* package in PEAR if it deals with adding, editing, deleting user data like firstname, lastname, email, affiliation, etc. This will become a hassle to find a general purpose solution as such data can vary a lot accross applications. We would enter a standardisation process looking for the common denominator of vocabulary to describe user data - and we would have to offer a mapping mechanism for existing solutions. As far as a new permission package is concerned, it is sufficient to relate the ID of a user from the permission schema to a self-made user data schema. Maybe I understood something wrong here? Perm_LiveUser +1 I am very much in favour of adding those parts of Markus' LoginUser class which deal with permission issues to PEAR - and I would certainly like to contribute to that. Markus' classes are an excellent starting point! I'd propose the following approach towards a new permission package: Perm/ Some abstract permission classes which handle the basic permission methods and provide containters to access different data sources (e.g. flat files, XML, RDBMS, SOAP, LDAP, ...) as well as the relevant default schemas (e.g. XML schema, RDBMS table definition, ...). Perm_LiveUser/ Extending the Perm/ abstract classes, providing a special purpose API. Perm_*/ any other permission package, e.g. the 'simple' permission classes. Sandro > As I wrote earlier we have no other choice but to name things randomly, > because if we put "information" (like "complex") in the name we might > have issues when a new package comes along. > > LiveUser is fine. > > So split the package into the above mentioned three packages. > Name the Container subdir "Container" and not "Containers" and lets be > done with it. > > > +234423904239023 > > Regards, > Lukas -- Sandro Zic oc4ware Project Manager oc4ware - Software 4 Open Communities http://www.oc4ware.org oc4 e.V. - Association of Open Communities http://www.oc4home.org