Wow, I can't believe this debate is ... so heated. The guy just wants to host a few pages on his home connection, I doubt the page is going to be a high profile target for any non-obvious 0-day security vulnerability (all major http daemons have had their fare share in recent years)
Nor are the performance differences going to matter for a few likely static pages. My advice, if the original poster hasn't run to the hills IIS [Consumer/Limited flavor] Pro's: 1. GUI Interface for setup. therefore you might find it more intuitive IIS Cons [I'm not up to date here, unfortunately]: 1. Limited to 10 concurrent connections (maybe less?, not really an issue though here) Apache Win32 Pros: ( www.apache.org ) 1. Flat httpd.conf file for setup, which is fairly simple if you read the comments, also makes one-step restoration of default settings and soforth possible 2. No connection limits or anything of the sort Apache Win32 Cons: 1. httpd.conf isn't always that simple, especially at first I personally prefer Apache2 Win32 for my own similar small stuff, since the artificial connection limit of IIS bothers me on a subconcious level, and I feel more at home with a .conf file than an obfuscated GUI, But that doesn't apply to everyone. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
