Re: Can't modify EO objects! ARGH! =(
Re: Can't modify EO objects! ARGH! =(
- Subject: Re: Can't modify EO objects! ARGH! =(
- From: Art Isbell <email@hidden>
- Date: Mon, 21 Jul 2003 21:26:09 -1000
On Monday, July 21, 2003, at 08:57 PM, Giorgio Valoti wrote:
On Martedl, lug 22, 2003, at 02:55 Europe/Rome, Art Isbell wrote:
On Monday, July 21, 2003, at 02:17 PM, Jonathan Rochkind wrote:
Also, unfortunately, once you start using multiple ECs, you need to
take care of LOCKING them all.
Only if one uses concurrent request handling, right?
I think that you should take care to lock anyway.
If I read the WO 5.2 documentation correctly, a nested editing context
uses the lock of its parent, so if its parent is the session's default
editing context, there's no need to lock it.
Locking does impose a small performance penalty and can lead to
deadlocks if not done correctly.
Concurrent request handling is a WOF feature.
True, but unless the programmer creates new threads herself,
concurrent request handling will be the source of the multiple threads
that an editing context might need to deal with. So in the usual
situation without concurrent request handling (i.e., no
programmer-created threads), is there any exposure of an editing
context to multiple threads? I don't think so, so locking would seem
to be an unnecessary action.
Aloha,
Art
_______________________________________________
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.