I use the Peer object model to map the DB. So I have BaseObjects.
If I have two clients connecting to Turbine, retreive for example the list
of TurbineUsers and modifing the same BaseObject (for example turbine user).
The first client save it to persistant storage, then the second client save
the modifications too. It will crush the first modifications.
How could I lock this object for all the clients ?
Do I need to add a LastModified column for every table of the DB, so that
before saving, I checked that nobody have modified it before I save ? Is
there an other solution ?
I think, I'm not the first one with this problem. How do you revolve it ?
Thanks,
Herv�
>
>
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
