• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

apache for win 2k, any good?

certainly better than IIS! No seriously, it all depends on what kind of content you're serving. Apache uses the fork() method of handling incoming connections; that is, one httpd process per connection. These take some time to time out and can sometimes run out of control. IIS uses a single multithreaded process to handle all incoming connections. Both models have their advantages; I find apache more flexible, less swiss-cheesish and much faster for my own use, YMMV!
 
There's nothing wrong with IIS, nor is Apache a bad choice either. Both require proper Administration and setup, and contrary to some people's opinion of IIS it can be made secure. Most variants of Nimda and Code Red would have been null and void with proper administration from the beginning.

With that being said Apache is, in it's own right, a good web server application as well. As a matter of fact the AT forums run using it last time I heard. The reason that Apache was chosen over IIS, IIRC, was due to Apache having a better compression ratio, not because IIS couldn't be made secure.

In case you haven't already found it you may want to check the Apache page out.
 
Apache is in my opinion the superior webserver for most uses. But Im a UNIX biased geek. There are rumors that Microsoft is using some Apache code for IIS6. I think its a great idea 😉
 


<< certainly better than IIS! No seriously, it all depends on what kind of content you're serving. Apache uses the fork() method of handling incoming connections; that is, one httpd process per connection. These take some time to time out and can sometimes run out of control. IIS uses a single multithreaded process to handle all incoming connections. Both models have their advantages; I find apache more flexible, less swiss-cheesish and much faster for my own use, YMMV! >>



I don't use Apache for Win32, but I was under the impression that on Win32, Apache uses native threads. Context switching in the NT kernel is massively expensive.

Under Unix, fork() was largely implemented for reliability reasons, and I think the results speak for themselves.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top