Quote:
Originally posted by RawAlex@Jan 26 2003, 07:36 PM
Eric, all of this is nice, except you miss the most important part of ths discussion:
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
|
Hi Alex,
Quote:
|
Windows NT (or XP) has alot of things running on an IIS server that are not needed directly for serving content.
|
Umm, First Windows NT is very old. That term is not used much anymore.
IIS comes with an SMTP mail Server and an FTP Server. You specify if you want these installed during setup of IIS. Personally I use Windows 2000. I really didn't care for XP.
A Windows Server is MUCH, MUCH more than just a simple Web Server.
You are right there.
There are a ton of things you can do with a Windows Server.
I AGREE that if all you need is a Web Server and a Database....stick with Linux, PHP and MySQL.
Last edited by EricP at Jan 26 2003, 07:51 PM