MultiECLockManager. Set and forget ?
MultiECLockManager. Set and forget ?
- Subject: MultiECLockManager. Set and forget ?
- From: Owen McKerrow <email@hidden>
- Date: Thu, 26 Apr 2007 10:12:05 +1000
Hi All,
Im looking at cleaning up our locking procedures on some of our
projects. Looking over past emails and on the wiki the most commons
suggestions are either MultiECLockManager or Project Wonders ERXEC.
We're not using Wonder at the moment so Im thinking
MultiECLockManager. I seem to remember Chuck once implying that it
was basically a set and forget sort of thing, that once you had
registered you EC with it you didn't need to worry about locking
anymore. Is this really the case ?
What we have on the current project is a base component that all of
our other components extend from. This base component contains a
variation of Chucks CoOperatingEditingContext (thanks Chuck), so each
of our pages has their own EC with session wide variables, like who's
currently logged in, being stored in the default editing context.
What Im wondering is if I was to use MultiECLockManager and it is as
simple as it seems, all I should need to do is in my base component
when the EC is created, register it with the Manager and then go back
through all of my code and find any ec.lock(), ec.unlock() and remove
them.
Am I understanding this correctly ?
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - -
"I like the way this project has somehow, against all common sense,
got itself made."
- Peter Jackson, "The Lord of The Rings"
_______________________________________________
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