IMO servak is insufficient.
You have to go a big step beyond the idea of a web-server component - and instead - think about the container as the web-server. Imagine a web-server that is containment platform. Imagine that the containement platform is extended to provide an HTTP interaction and session management layer.
I think I agree. When we look at Tomcat, then we find a number of container-component notions in it. Tomcat has web applications, deploy/undeploy, management, in short: it's a platform for hosting web applications.
If we think of Avalon/Container as a platform for hosting server applications then web applications are a subset and should be supported on the same level as other server applications. Only then can web applications benefit from all the neat features of the Avalon framework.
The way it is now, we need to host Tomcat (or Jetty or whatever) and have it host web applications. Of course this is better than no web connectivity at all. I'm sure if there were some kind of community around this idea, then more advanced integration strategies would follow.
Ulrich
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
