Locking Objects

[Rick Waugh]

I've created this lovely little object oriented application, where I'm
retrieving the data for an object, and storing it as a session variable for
someone to work on. The problem comes in record locking - how do I lock those
records - I want to have an error message come up to tell someone else that the
data is already locked.

I'm considering using an application level object, that keeps a list of data
being updated, that would be checked whenever someone tries to edit. My
question is around locking - if I create an application object that keeps an
array of structures, each structure representing one locked piece of data, do I
need to use CFLOCK to lock the entire application level object when it is
updated, or just the array inside the object?

Thoughts, opinions, warnings, am I driving off a cliff?

[emanweb]

Hi Rick,

I think there is a missunderstanding on the cflock usage here 9if you
use google for cflock will find a lot of good resources). What I
understood about what you want to do is a system to avoid concurrent
access to the data object that someone is already having access. In
this case what I recomend is creating a repository of data where you
store the user id and the object id, then query this repository
whenever someone needs to access any object.

sorry for my poor english.

HTH

Emanuel Costa