Re: another Auth-class
| From: | Wolfram Kriesing | Date: | Tue, 30 Oct 2001 08:27:05 +0000 |
| Subject: | Re: another Auth-class | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-2434@lists.php.net to get a copy of this message | ||
> Do you manage user rights, groups and profiles ? User rights should
> not be restricted to Read, Edit and Delete. You should be able to
> define any kind of right (Download, Drill-down, etc...), group
> users and define profiles.
well currently this is not managed, but as you know those classes can
simply be extended
the problem why i have not implemented those kind of things yet is
that i didnt find a convincing way yet without putting restrictions
on those people who use the class, i am not a friend of saying: when
u use this class your DB has to look like this,
configuring the class seems better to me, but sometimes too many
parameters do also confuse
if you know a nice way, how to implement this in those classes lets
discuss it
> Also, there should be a possibility to define rules triggered
> during permission checking.
what do you really mean by that "rules triggered during permission
checking" ? please give an example
> It is very important to be able to display a minimal GUI for
> incorporation in target applications.
you mean stuff like login page?
i dont think so, my classes have _no_ html inside and dont return no
html, i think this is up to the user to design the page etc.
everything that goes out and can be seen should be made up by the
webdesigner not given by an API, i think
so again _my classes dont produce no html output_ neither for the
login screen, nor for any other screen
wolfram