On 24-Jun-09, at 8:28 AM, Mike Schrag wrote:
Could that be a typo?
You'd think so, but no. Seriously, that is the setting that I use.
And yes, I do use the sec to serve up most of the public content.
So wait .. is that setting broken, or does it just not do what i
think it does?
ms
er.extensions.ERXEC.useSharedEditingContext=false
That setting sets all regular ec's shared editing context to null ...
so they don't have access to the shared eos. You can still bind
objects into the sec ... but no other ecs can see them. If this
setting is true and you use the shared context you get weird recursive
read locking errors on high volume sites. I was bit by this
earlier ... I used to love the shared editing context. Perhaps it's
just me who experienced this? :) ... i now use the "false" setting
and my deadlocks went away.
Cheers,
Michael.
_______________________________________________
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]
