I'm no expert on tomcat, but AFAIK, tomcat is supposed to be a very
configurable "skeleton" of a servlet container.
Thus, you can configure it with plain vanilla everything (including a a
plain vanilla http server ;-) and call it a reference implementation. This
will look externally very similar to the JSDK.
OR, you can configure it with everything (including a connector to apache,
JAAS authentication, interceptors to do all sorts of things like fail over,
etc) and call it a production quality engine. This will look externally like
JSERV.
does that address your concerns?
cheers
geoff
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
