slow windows httpd server

[Walter Giesbrecht]

On Thu, 25 Jan 1996, John Adder Fink wrote:

> It sort of weirds me out (and no offense to the original poster meant; nor 
> to anyone who has a similar setup) that a university or a library would 
> be using as their *primary* web server something as network-hairbrained 
> as a Mac or Windows machine.  The time and effort put into learning how 
> to set up a UNIX or other high-end platform would pay exponentially.
> 
> My advice?  If it weren't obvious by now... :)  scrap the Windows and 
> stick Linux on that 486-66, serve your documents from NCSA httpd.
> 

... on the other hand, the experience gained in setting up a WinHTTPD 
server is readily transferrable to using something like Website on a 
Windows NT platform. Not that I mean to start another OS war or 
anything :) I considered running our library server using Linux, but 
decided that the time required to get up to speed with it (Linux) was 
too much, given everything else I had to do. My Website server is 
performing perfectly adequately (for now, anyway). I agree, though, 
that Win HTTPD should be considered only as a stop-gap measure (as it 
was for me), while you wait for something more robust.  

BTW, does anyone know of (or had any experience with) comparing an 
NT-based server with a Unix-based server on the same hardware? 
Just curious ...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Walter W. Giesbrecht               walterg at yorku.ca    
York University Libraries 
http://www.library.yorku.ca