Re: locking editing context
Re: locking editing context
- Subject: Re: locking editing context
- From: Brent Shank <email@hidden>
- Date: Mon, 17 Feb 2003 11:22:33 -0800
Perhaps this will help:
http://developer.apple.com/techpubs/webobjects/Enterprise_Objects/
Concurrency/chapter_11_section_3.html
Also, the WebObjects examples are a good source of sample code that
locks and unlocks ec's when needed.
Brent
On Thursday, February 13, 2003, at 06:40 AM, Serge Froment wrote:
Hi Jonathan,
Le mardi, 11 fiv 2003, ` 12:30 America/Montreal, Jonathan Rochkind a
icrit :
This whole issue is definitely my biggest annoyance with WO. It would
be nice if Apple provided a definitive explanation of locking of ECs,
addressing both nested ECs, peer ECs, and the defaultEditingContext(),
with and without concurrent request handling, in a clear way. And also
providing example code that handled locking in a way Apple guaranteed
was appropriate.
I totally agree. This is not clear to me, also, when do we actually
need to lock editing contexts. Calling EOEditingContext.insertObject
surely needs a lock, but do we need to lock when we call
faultForGlobalID, or globalIDForObject? If we actually need to lock in
those cases, then this is scareful since
EOUtilities.localInstanceOfObject does call those methods and it does
not lock the editing context! In this case, how can we know all cases
where we should lock editing contexts aside decompiling the whole
WebObjects code?
Serge
_______________________________________________
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.
_______________________________________________
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.