> IIS? Who cares.
Well, for many reasons, some of us do.
First, there are distinct advantages to running IIS over Apache on NT in
certain production settings (like better integration with FrontPage, ease
of management using MMC, ease of integration with other MS products, access
and authentication control using Active Directory). These cannot be
discounted as legitimate needs of users who might prefer Tomcat for dynamic
content and IIS for static content.
Second, Apache on NT is far from clean. On average, I have to reboot it two
to three times a day in order to keep it from crashing due to too many
memory errors. Of course, one could blame the operating system, but that
ignores the fact that for better or worse, some MIS shops are forced to
deploy NT/2000 and do not have the resources or talent to either go to
Unix/Linux/BSD whole hog or even support a few scattered machines. I had to
drag one of our clients kicking and screaming into Unix so that I could put
a sendmail front end on their horrible Exchange mail router. I don't think
that they would buy doing that again for web services (which they want to
manage).
Of course, one MIGHT argue that Tomcat has no place in a production
environment, but that would be patently ridiculous since why else would
anyone want to develop WITH it.
So, don't blame the developers who have to work on NT/2000. They are often
constrained by the realities of the production world where systems like
Tomcat get put through their hoops.
Sean McLinden, MD
Outcome Technology Associates, Inc.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
