Re: locking editing context
Re: locking editing context
- Subject: Re: locking editing context
- From: Art Isbell <email@hidden>
- Date: Mon, 10 Feb 2003 17:33:18 -1000
On Monday, February 10, 2003, at 09:29 AM, Jonathan Fleming wrote:
do you have to lock & unlock the editing context only when you are
using a steless section (directActions) of your application or do you
have to lock & unlock it in state as well?
Locking isn't necessary unless you are writing a multithreaded app.
Writing and debugging a multithreaded app is so difficult that it
should be avoided unless you really have no choice.
What about the defaultEditingContext(), does that need locking &
unlocking too?
Never
Whith this I have never seen any examples that lock the
defaultEditingContext() so I'm presuming you don't need to lock &
unlock, but I don't want to presume, I prefer to know. The API isn't
making it clear.
What's New in WO 5.2
(http://developer.apple.com/techpubs/webobjects/WhatsNew/index.html)
includes a section "Concurrency and Locking" which answers your
questions.
Art
http://homepage.mac.com/aisbell/
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.