Re: Concurrent request handling
Re: Concurrent request handling
- Subject: Re: Concurrent request handling
- From: Chuck Hill <email@hidden>
- Date: Thu, 10 Mar 2011 08:22:34 -0800
On Mar 10, 2011, at 1:22 AM, Gennady Kushnir wrote:
> Hello all !
> I am wondering whether to turn on concurrent request handling on my
> deployment or not.
I always have this on.
> What are potential drawbacks of this? I assume there should be some.
> Why would it be off by default otherwise?
> I could not find anything interesting on this in documentation.
WebObjects has several defaults that are not what most people would want. I think these defaults were set to preserve existing behavior when new features were added. Unless you are sharing unlocked global writable data (from static ivars or Application), there is no reason to NOT have this on. If you are sharing unlocked global writable data, then you are Bad Person and should fix this!
> And another question: would concurrent request handling save me from
> global application deadlocks when one single request locks on
> exception?
Maybe. It depends on why that session/request is deadlocking. I would focus on fixing that.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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