If there was an LDAP schema for portal preferences would that change
your view?
I am attracted to the idea of a single data repository but do not know
enough yet to know how hard that would be to implement or whether it
would be more grief than benefit.
Microsoft has certainly put a lot of its data into Active Directory and
the Windows Registry which are both hierarchical
rather than relational. Searching is not as easy as with a relational
database but the access is down a line of keys LDAP seems pretty fast
and it seems easy to provide useful tools which are not application
specific.
Ron
Aaron Evans wrote:
Furthermore, if I understand correctly that user portlet preferences
and user traits/attributes are both being stored in this medium, IMHO, I think
that these should be seperated out.
The storage of portlet preferences involves storing arbitrary keys and values.
But user attributes are generally going to be made up of a list of fixed
attributes for a specific portal implementation (eg. email address, first
name, last name and a whole host of other information that will be necessary
to maintain).
At least in my case anyway, I am not interested in storing portal preferences
in LDAP as the schema will not really allow for this. However, I do want
to maintain all the other fixed user traits in LDAP and have them loaded by
the user manager to possibly be made available to portlet applications.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
