Notification between EODataContext using project wonder today
Notification between EODataContext using project wonder today
- Subject: Notification between EODataContext using project wonder today
- From: "Andreas Hjortsberg" <email@hidden>
- Date: Mon, 18 Jun 2007 19:36:21 +0200
Hello,
Using WO 532
I have to ways of booking transactions through my application. One by direct actions which uses only one single EOEditingContext and the other one which is a component, a separate EOEditingContext for every Session.
This is nothing strange I suppose. The problem occurs then two transactions that share data is updated at exactly the same time, and I mean data on a row level in the database.
It is extremely rare that it happens, once every second year or so but it is a big problem.
One solution is be to book all my transactions through direct actions, this will solve my problems for now, but in a while we will start with multiple instances and then my strategy will fail as then I need to synchronize the contexts between different instances.
So whats the best approach for this matter, Is there away to notify my other contexts that the data has been changed as it don't seem to happen today?. Should I use locking? I thouth project wonder was handle that issue? Or should I always invalidate the target object but then I always will invalidate the object for every transaction. Can I use changesFromSnapShot together with comittedSnapShotForObject to check if my object has been altered in another context?
Any thoughts's
Regards
/Andreas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden