Ok, I understand that, but I could use for example, in one component a
MECLM's registered editing context, in another a ERXEC, in another a
editing context with manul locking, etc.?
On Nov 18, 2005, at 1:29 PM, David LeBer wrote:
On 18-Nov-05, at 2:18 PM, Marcos Trejo Munguia wrote:
Hi Chuck.
I was wondering if I have to use the MultiECLockManager in all my
application or I can be selective?, I don't know if being selective
can cause me problems (more deadlocks).
You don't *have* to do anything :-)
MECLM is an implementation of a generic pattern for managing the
locking of multiple ECs.
If you don't use multiple ECs in your application then you won't need
the MECLM (ie: only use the Session.defaultEditingContext()).
Alternately, there are alternatives:
You could use ERXEC from ProjectWonder, or you could roll your own, or
you could lock all of your ECs where and as you use them - with the
caveats raised in Chucks book.
Finally, if you aren't using a Session in your application then the
MECLM is not the right choice.
The choice is yours.
--
;david
--
David LeBer
Codeferous Software
'co-defer-ous' adj. producing or containing code
site: http://www.codeferous.com
blog: http://david.codeferous.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
