-----Original Message-----
From: David Ramsey [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 06, 2000 10:48 AM
To: Turbine
Subject: Non-database sources of user information
>I've been given a task to look at extending Turbine for our own use but
>we have user authenication and authorization information in persistent
>storage formats other than relational databases.
>
>At first glance, the TurbineUser.retrieveFromStorage appears to be
>pretty closely linked to the Criteria class and that seems to be built
>from the ground up with relational databases in mind.
>
>My first thought is to push an intermediate class between TurbineUser
>and Criteria and let that class handle the choice between a database
>source and other sources of user data but I am also interested in
>hearing what others might be doing, assuming that anyone has a similar
>problem.
I'm in exactly the same position, trying to use LDAP rather than an
RDB for user info storage and retrieval. Like you, I've found the
RDB assumption to be pretty deeply wound into the Turbine user-related
classes. Any pointers on ways around this from this list would be
extremely helpful.
(I've approached the problem by subclassing TurbineUser and overriding
the retrieve and store methods, but there are many other places that
assume that data is available from an RDB, SQL-accessible, with a
Visitors table. Examples available if needed.)
--
Craig Berry
GlueCode
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
