Re: locking problem
Re: locking problem
- Subject: Re: locking problem
- From: Chuck Hill <email@hidden>
- Date: Mon, 20 Dec 2004 07:30:17 -0800
You are reading too much into that statement regarding ERXEC. Those
were just some example situations, _not_ an exhaustive list. You
_can't_ lock like that in your component code due to the effects of
binding synchronization. You might be able to do it if you heavily
modified the EO code, but it is not worth it. At better statement re
ERXEC is that is locks during any operation which may result in state
changes or access to lower level frameworks. I've not seen the code, I
don't know how extensive this is (how many methods are affected), but
it would guess that lot's of methods on EOEditingContext would would
potentially result in a state change or lower level access.
Chuck
On Dec 19, 2004, at 2:50 PM, Nathan Dumar wrote:
In reading a discussion thread about ERXEC recently, Anjo said that
ERXEC only locks during the "dangerous" operations, like save, fetch,
etc. So, that's what I'm doing now -- putting locks in the try block,
before any fetch or save, and unlocking right after, in the finally
block. From what I've read, this seems to be the best solution, but
I'm always open to learn more. If anyone has suggestions, ideas,
warnings, or whatever, please post.
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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