On Wed, 29 Aug 2001 19:14, Paul Hammant wrote:
> Peter Donald wrote:
> >+1 to idea of UserManagement Block
>
> For just FtpServer or should James and FtpServer find commonality and
> make a cornerstone "service" style block ?
If it can be done. First it may be best to just refactor inside ftpserver.
Then look at commonalities and other User systems (like jetspeed+turbine,
james and ftpserver) to see where they overlap. I think the commonalities are
essentially.
Every API has notion of "user". Associated with each user are a number of
"attributes". Example attributes could be username, password, home directory,
mail spool, Human presentable name etc. In some cases you may even allow
complex-types/objects to be associated with a User.
The actual implementation could arbitrarily map this to any underlying
format. Some underlying formats include;
* database
* NT Realm
* Unix /etc/passwd
* LDAP
* simple xml format
* YP directory (or whatever it is called nowdays ... ndis???)
etc.
Each has a different "schema" and allows different set of attributes.
Hopefully when constructing UserManager you could specify appropriate schema.
At one stage I was talking about this and you can see the start of it in
cornerstone.services.security. However the company I was writing it for went
under so ... ;)
--
Cheers,
Pete
---------------------------------------------------
"If you don't know where you want to go, we'll make
sure you get taken."
Microsoft ad slogan, translated into Japanese.
---------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
