IMHO things you could do with tomcat. Create Java based Web Application. Utilizing Servlets, JSP, TagLibs. If required (really required) use EJB along with the web application. The servlet specs is designed to create web application and not just serve pages.
Tomcat should be only treated as a servlet container and nothing else as that what it is. It is reference implementation of servlet and jsp specs. HTTP Connector is added to it so that can be also used in stand alone mode. A webserver is primarily used for serving pages, it can use support from different application system for delivering content and one of these application could be tomcat(servlet container), coldfusion, mod_perl, php or simple CGI application. Web server can act as an intermidiatory or as a filter for forwarding the request to the respective applicaiton handlers. Tomcat can not do this. It is also not wise to use TOMCAT's resources for something which it can do, but is not built for, e.g. sending your huge movie file or mp3 download through it. It can do it but you would probably want a webserver to handle such request. And ultimately it boils down to performance, you should choose whatever configuration gives you the maximum performance/cost benefit. Thanks, -SN -----Original Message----- From: sonam singh [mailto:[EMAIL PROTECTED]] Sent: Saturday, October 12, 2002 1:23 AM To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Why to use Apace as web server with TOMCAT that is true serving the static content from the tocmat is slow as compare to the apache . ua have to use the apache for static content and rest for the tomcat . we are using in apache + tomcat .in order to connect the apache with tomcat use mod_jk .u can mail me for further help on [EMAIL PROTECTED] regards Sonam Singh -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
