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: Thu, 9 Apr 2009 13:17:26 -0700 (PDT)
Thanks for your time and advise Guido.
--- On Fri, 4/10/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: Friday, April 10, 2009, 1:28 AM
On 9. Apr. 2009, at 12:46 , shravan kumar wrote: > Now am using ERXEC.newEditingContext() for creating new EC's, manually locking/ unlocking where required. Also locking/ unlocking in awake/ sleep respectively respect object bindings in the component. As long as you don't subclass ERXApplicaton and ERXSession, that won't help you much over using
EOEditingContext. You might grap the code related to autolocking and incorporate that in your app, but I'd avoid that. If you want to use MultiECLockManager - unfortunately I never used it and I don't have a download source. The links here: http://wiki.objectstyle.org/confluence/display/WO/EOF-Using+EOF-Context+and+Database+LockingSeem to be dead again (wocode). 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