Santiago Gala wrote:
> data.getUser() returns a User. We want to edit information using old ways (i.e.
> the database). What would be the right way?
Now the system is made flexible to accomodate data stores other than
databases.
I'm thinking about directory services (most notably LDAP).
> - Update fields in the User object and let Turbine save it to the DB. I think
> that we are not using anything that is not in the new schema, so this should be
> a way. That looks simple, but I'm not sure on how to do it.
You should stick to this method if you want your application to be
portable
to all environments and configuration that Turbine supports.
> - Use the database (the old actions code did this). In this case, we miss the
> getId() method in User. We need to cast a User to a TurbineUser to get this
> method. Would it be safe to assume this? Else, would it be safe to assume that
> every kind of user will have some sort of unique numeric id, and thus add this
> method to the User interface? (That would be a very simple patch, if it makes
> sense.)
In a directory service, there are no numerical id. Every record (for
example
user) has unique Distinguished Name. The security code in Turbine
enforces
uniqueness of login names. You should use this value as a foreign key in
your
tables. This way your system will be compatible with both DB and DS
environments.
> The code we are porting is relatively old. We don't understand so well the new
> model... The situation is not ideal, as you can see :)
I suspected that bringing Jetspeed up to date with Turbine will not be
an easy
task because many important things changed in Turbine during the past
months...
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
