Hi Quinton;
Embedding jetty is a very interesting idea because it's actually a pretty decent web server for serving static content and copes well under heavy load. If you were to embed Jetty and then port the WOAdaptor to Jetty as a plugin / filter / servlet (or whatever it uses), you would have a "WOAdaptor/wotaskd" app to replace wotaskd, (as in the diagram), but it could serve as both a front end / load balancer replacement for apache or as a load balancer agent for apache or some other web server (responding to WOAdaptor, mod_balancer and whatever other protocols). This would make small deployments VERY easy because you could replace apache completely, but traditional deployments would continue to work as they have always done. You would then have the option of using either mod_balancer, a WOAdaptor plugin like mod_WebObjects (but not limited to apache), or go direct to the "WOAdaptor/wotaskd" wo app for your front end.
That's another interesting way to look at –– using Jetty as a front- end like this could be flexible and yet potentially also simple as you have pointed out. I guess to achieve what we have now, there is the additional need for a Jetty proxy/front-end to "discover" other instances from some sort of pre-configured list of other Jetty-s running on other hosts. Rolling the monitor as basic JSP or something simple into the proxy is an interesting idea as well because it could potentially further reduce the complexity of deployment.
BTW; I'd be hesitant to suggest Apple use Jetty's internal connector API's as there is a risk of coupling WebObjects releases to Jetty releases -- a servlet is probably a better interface to be tied to.
cheers. ___ 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]
