Radicore Forum: How To » Concurrency / freshness of data objects

Home » RADICORE » How To » Concurrency / freshness of data objects

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

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

Report message to a moderator

[Message index]

		Concurrency / freshness of data objects By: Kiple on Thu, 23 November 2006 16:13
		Re: Concurrency / freshness of data objects By: AJM on Thu, 23 November 2006 17:39
		Re: Concurrency / freshness of data objects By: AJM on Tue, 05 December 2006 06:14

Previous Topic:	[tip] Changing scrolling order outer/middle table
Next Topic:	overruling primary validation time fieldtype

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sat Jul 12 20:50:17 EDT 2025

Total time taken to generate the page: 0.19950 seconds