Re: [rfc] permissions managment
| From: | Markus Wolff | Date: | Tue, 13 Aug 2002 17:32:11 +0000 |
| Subject: | Re: [rfc] permissions managment | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-8392@lists.php.net to get a copy of this message | ||
On Tue, 13 Aug 2002 17:55:23 +0200
"robert janeczek" <rashid@ds.pg.gda.pl> wrote:
> > I want the "complex" perm class (aka LiveUser) to offer it's features in
> > layers. And this is quite possible. Therefore "complex" will sort of
> > include "simple".
> >
> > This would have the advantage of making it easy so grow.
> > So I don't really see much reasons to have a separate "simple".
>
> the main reason of my proposition of simple perm class is that it should be
> easy to administrate. do you think your class could do that? i know that the
> most complex class can make everything that simpler ones can, but have in
> mind php developers who will be using it - i would be scared if i would want
> to write simple web site and have to use your administration page (or write
> my own). so - let`s create something really simple where is no need for such
> complex solutions.
I´ve had this discussion with Lukas on IRC. I´m always a big fan of
solutions that are simpe to use, powerful, easily expandable and well
documented - all at the same time :-)
Currently, the LiveUser class (working title) can be fully configured
and used with no more than three lines of code, providing the most
common settings. However, you can always dig deeper and have just about
anything configured to your specific needs. Point is, you don´t _need_
to learn or do much to use the class, which is pretty essential if the
class is to be used by many developers.
Having too many different permission classes leads to the same situation
we´re in now: Almost every PHP application has its own permission system,
making them all incompatible to each other - programmers who want to
integrate more than one program have to go through a real pain to make
the applications "talk" to each other, so the end users don´t have to
apply for more than one account on the same website.
Even if another app that you want to integrate uses another permission
system, integration becomes easy with LiveUser: Just write a new backend
class that knows about the other app´s different data structure and
you´re done.
Regards,
Markus
--
Markus Wolff <wolff@21st.de>