Given how close "mod_balancer" is to the traditional WO deployment,
it might be a nice approach for "mod_balancer" to take on-board the
few additional concepts necessary to support something which works
like "JavaMonitor / wotaskd" so that deploying a WO system does not
need a special Apache module compiled for it. That would make a
whole heap of documentation and confusion go away.
Yeah, this is actually exactly what I referring to :) Something like
we're used to with JavaMonitor controlling the proxy balancer module
would be very handy.
Another thought which may reduce the deployment documentation/
development overhead and ease-of-approach for newbies is that WOA's
could be built into servlets all the time, but that there is a
"special servlet container" built into WO runtime that can launch
the app in a way which resembles a stand-alone execution of the
application without the palaver that often goes with servlet
deployments. This idea may be quite nice.
So are you suggesting that WO should ALWAYS be running as a servlet,
just that WO itself has a tiny little servletish container in it that
it uses for directconnect?
ms
_______________________________________________
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]
