Alexander Leykekh said: > -- small application server vs. full-featured one, like Tomcat -- the > latter has much better chance to adhere to standards should you need If everyone here chose (percieved) standards over good technology, non of us would be here to begin with.
> portability in future, or decide to couple servlet-capable Web server > with Java application server. If the J2EE server has a built in http server, that can be much more (and is!) efficient then using a plugin. When you do not want to use a web interface, don't use it and it sits idle, nothing lost. That is not to say that I don't think a JK2 module for AOLserver is not a good idea, it is a great idea. More and more enterprise back-ends will be using J2EE and if AOLserver can interface with those, that is a greta thing. > > Alex > > > > I. To remove yourself from this list: > > Send a message to "[EMAIL PROTECTED]" with the following text > in the BODY of your message: > > signoff aolserver > > II. For a complete list of listserv options please visit: > > http://listserv.aol.com/ > > III. For more AOLserver information please visit: > > http://www.aolserver.com/ I. To remove yourself from this list: Send a message to "[EMAIL PROTECTED]" with the following text in the BODY of your message: signoff aolserver II. For a complete list of listserv options please visit: http://listserv.aol.com/ III. For more AOLserver information please visit: http://www.aolserver.com/
