Re: EOEditingContext Lock/Unlock best practice?
Re: EOEditingContext Lock/Unlock best practice?
- Subject: Re: EOEditingContext Lock/Unlock best practice?
- From: shravan kumar <email@hidden>
- Date: Tue, 7 Apr 2009 23:43:21 -0700 (PDT)
Thanks Guido. I really appreciate your quick response.
For setting the locking property mentioned, does my app need to extend ERXApplication? currently my app is very loosely coupled to Project Wonder i.e., we use different API's from Project Wonder as needed.
Moreover, after setting this property should I lock & unlock EOEditingContext in R-R loop or while fetching, saving, or modifying any EO object.
Please advise.
Thank You So Much,
Shravan Kumar. M
--------------------------------------------
--- On Wed, 4/8/09, Guido Neitzer <email@hidden> wrote:
From: Guido Neitzer <email@hidden>
Subject: Re: EOEditingContext Lock/Unlock best practice?
To: "shravan kumar"
<email@hidden>
Cc: email@hidden
Date: Wednesday, April 8, 2009, 2:20 AM
On 7. Apr. 2009, at 13:35 , shravan kumar wrote:
> "Question: Given these caveats and any other, please advise me *BEST PRACTICE* (that overcomes dangerous locking/ unlocking issues like: deadlock and ...) in locking/ unlocking EOEditingContext object in various scenarios like, the ones described above."
Use Wonder with
er.extensions.ERXEC.safeLocking=true
cug
|
_______________________________________________
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