| Concurrency / freshness of data objects [message #419] |
Thu, 23 November 2006 16:13  |
Kiple
Messages: 5
Registered: November 2006
Location: Surrey, UK
|
Junior Member |
|
|
Hi,
First let me say how much I like the Framework, diving into the code has been a good learning experience.
I think I may have missed something. One of the key problems is the risk that the data you are editing is not the latest and someone else has changed it. The delay between when you read the data to start editing and the point when you commit the changes can be substantial in computer terms.
I have seen some business objects that check for changes before the update or delete process and fail if there has been an update.
I can't see how Radicode protects against this. Is it locking at the business rules level?
Regards
Kiple
|
|
|
|
Radicore Forum
Search
Help
Members
Register
Login
Home
