Re: WO blocking/threading question
Re: WO blocking/threading question
- Subject: Re: WO blocking/threading question
- From: Hsu <email@hidden>
- Date: Mon, 16 Aug 2004 10:34:39 -0700
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.
For the moment, yes, that's probably true.
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.
It's not. It might be possible to setup multiple servlet containers on
a single machine, and load-balance or cluster between them, though.
Obviously, it's possible to have multiple machines with 1 servlet
container each and do that as well.
As before, it might be possible to mitigate some of these effects using
multiple EOF database channels.
If this is the case when is it appropriate to use SSDD?
SSDD exists merely because many WOApps deal with filepaths, rather than
URLs; SSDD allows you to run your WOApp in a servlet virtually
unchanged. Using a "true" WAR requires that your app only reference
URLs. Practically, there is no difference in deployment behavior.
Dov? How do you deal with WO/EOF performance using the servlet
adaptor?
Mike
--
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.