> Can we ensure ( and I think it is a feature of Turbine ) that the
> authentication is separate from the storage of user settings that is needed?
> For example: We need to authenticate users against an NT domain ( or maybe an
> LDAP server ). Along those lines, maybe we want to store user settings in an
> LDAP entry for that user also. I guess what I am saying is it would be ok to
> require authentication/storage, but can it be designed to be pluggable
> authentication and pluggable storage? That way the users could be
> authenticated against LDAP for example, but all settings/session information
> for the user could be stored in an sql server.
+1. I also need to be able to incorporate external authentication (eg against
+existing e-mail accounts or using the DASCOM framework).
Somebody else mentioned win2k problems. To estimate the number of bugs compared to
previous versions, simply divide the current version by the old version and multiply
by 100%.
Example: Windows 2000 vs. Windows 98: (2000/98)*100% = 2040% more bugs
-ed
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
