[RawAlex]

Eric, all of this is nice, except you miss the most important part of ths discussion:

Windows NT (or XP) has alot of things running on an IIS server that are not needed directly for serving content. That includes the GUI interface of windows, the windows logon security system, and thousands of other little snippets of code and crap that have NOTHING to do with serving webpages - and have everything to do with using up system resources. IIS / NT just doesn't run well under load, when compared to the unix/apache combo.

The hole slammer used is a known one, but I can tell you, based on the number of updates I keep having to do to XP, I assume there are a pile of undiscovered bugs out there in microsoft stuff just waiting to be exploited.

Sorry, web servers don't have a GUI interface. Until microslop gets that idea clear, you are going to have bloatware with security holes... web serving is a simple straight forward thing... IIS/NT is just too complicated to do this right at any large scale.

As for ASP.NET, it doesn't matter - it runs on an underperforming platform, and as such, isn't going to set the world on fire until the underslying problems are fixed.

Oh yeah, I forgot: Microslop was caught not a year ago running unix/apache servers on some of their sites rather than IIS. it was funny to get an error page with apache on it.

Back to the game.

Alex