Hi,
> 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.
I have just started looking at something similar too.
> 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.
Not sure how this would help - I think you'd probably just have to write your
TurbineUser class - and it could then do whatever you want.
> TurbineUser.retrieveFromStorage
The "extreme" solution I have gone for is to do a custom version of the LoginUser
action - and rather than let UserFactory get and validate the user, I get a shell user
and then have a custom retrieveFromStorage that takes a username and password (thats
the way our login works) - and get that to do the accessing of the user storage.
See ya,
Chris
---
"surely it is madness to accept life as it is and not as it could be"
______________________________________________
FREE Personalized Email at Mail.com
Sign up at http://www.mail.com/?sr=signup
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
