Re: WO blocking/threading question
Re: WO blocking/threading question
- Subject: Re: WO blocking/threading question
- From: Hsu <email@hidden>
- Date: Sun, 15 Aug 2004 17:52:27 -0700
I've also done some J2EE development recently and in everything I've
read on J2EE, performance and memory footprint is always a primary
concern. What are other people's thoughts on this matter?
Heh. With any kind of scalable deployment, performance and memory are a
concern. I'd be surprised at any framework where it isn't.
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.
Karl
--
If your face were a tree, it would be different.
Homepage:
http://homepage.mac.com/khsu/index.html
_______________________________________________
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.