On 21 May 2002, Titus Brown said:
> -> I think UserKit would be somewhat usable, but it might be easier just
> -> to factor out the basic functionality from the MEMS Exchange's User
> -> and Group classes.
>
> Are you sure this belongs in the basic Quixote package?

I'm pretty sure that a simple, expandable User class belongs in Quixote,
along with some example code for a simple authentication UI.

However, anything belong user/password should be up to applications to
define.  I don't think Quixote should be in the business of roles,
privileges, groups, or any of that -- not even defining interfaces for
applications to implement.  Access control is just too broad and too
application-specific.

> (I'm never in favor of expanding things ;).

Good default position!

        Greg
--
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org