First, Tomcat can perform all of the basic web server functionality
that IIS can - it can serve static content over any port you configure it
to. IIS, however, has one thing going for it - its much faster than Tomcat
at the static stuff (I know, its amazing that anything Microsoft has
Let me ask you another question. Why would you use M$ products at all?
Original Message
On 2/14/01, 7:39:38 AM, "Tiseo, Paul" [EMAIL PROTECTED] wrote regarding
IIS Tomcat. Why?:
Please forgive a complete newbie, but I joined these lists to start
building my knowledge of servlets
1 11:40 AM
To: [EMAIL PROTECTED]
Subject: Re: IIS Tomcat. Why?
Let me ask you another question. Why would you use M$ products at all?
Original Message
On 2/14/01, 7:39:38 AM, "Tiseo, Paul" [EMAIL PROTECTED] wrote regarding
IIS Tomcat. Why?:
Please forgive a complete newbie, but
Any then for a REAL answer...
If you had a box that had existing IIS applications running and you
wanted to add servlets (and jsp if you really want a new nightmare).
You could tie the two together..
Or if you have a high-access site and you need the performance
for static pages and HTML you
you wanted to add servlets (and jsp if you really want a new nightmare).
I constantly see folks on this list referring to JSP as 'a new nightmare'.
I realize it's very easy to program 'poor' JSP, but what replacements are
there to handle presentation logic as easily (and separately) as JSP? I
Have a look at the "Getting Started" bit in the Tomcat- A minimalistic
User's Guide on http://jakarta.apache.org. The main point seems to be
regarding scalability and stability - Tomcat on its own isn't beefy enough.
Bear in mind this is the opinion of an almost complete newbie to Tomcat, so
I
