Hi Mike;
I spent a bit of time on this a few years ago and developed (and open-
sourced) an AJP WO adaptor (AJP is a binary stream for HTTP used
widely with Jetty and Tomcat deployment) to work with the built-in
Apache 2.2 mod_balancer / mod_ajp / mod_proxy / mod_???. It worked
really well, but after a while, one comes to realise that the bits
missing out of the Apache 2.2 "mod_balancer" approach which are
present in JavaMonitor / wotaskd are really quite nice. :)
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.
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.
Anyway... just ideas.
cheers.
I've since reinterpreted Bill's comment to mean "everyone in the
world of java" not "everyone in the world of wo" ... And I would
agree with that, and there are technologies that are actually very
similar to pieces of the WO deployment system that would be worth
investigating to find the ideal solution to this problem.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
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]
