Re: WO blocking/threading question
Re: WO blocking/threading question
- Subject: Re: WO blocking/threading question
- From: Michael Parlee <email@hidden>
- Date: Mon, 16 Aug 2004 00:26:20 -0700
What about deploying in a servlet container? The adaptor servlet
must be multithreaded as per the servlet specification, but does it
forward incoming requests to a single instance of the WO application?
Is that configurable somewhere?
See my earlier post. WO advertises itself as a multithreaded servlet
(which, by the way, is not required), but once the requests hit WO
itself, all of the WO behavior comes into play - if you have
WOAllowsConcurrentRequestHandling==false, all request handling will be
serialized. If you have WOAllowsConcurrentRequestHandling==true, all
request handling will be concurrent. EOF follows the same limitations
as a standlone application. Note that it is much easier to setup
multiple instances of standalone WO apps, than multiple instances of
J2EE containers, generally.
Thanks for your explanation, Karl,
I'm still a little puzzled about WO servlet deployment. It seems that
the jsp/servlet container is best suited to a multithreaded model for
concurrent request handling, but among other reasons, since EOF is
single threaded, running multiple instances is probably the best
approach to scaling WO apps.
Am I missing something or is it fair to say you're best off sticking
with multiple instances and the old school web server adaptor for
scaling WO apps? It doesn't appear to be possible to have the servlet
adaptor instantiate multiple instances of a web app within the same vm.
If this is the case when is it appropriate to use SSDD?
Dov? How do you deal with WO/EOF performance using the servlet adaptor?
Mike
_______________________________________________
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.