Andrew Hodgson wrote:
Does anyone know the actual status of HTTPD on Windows as a production server? I know lots of people use it, but I have seen articles (and so have others in the company) which suggest it is designed as a development platform, and not really intended as a production ready server.
That's absolutely true of 1.3 - threading was bubble gum and bailing wire, nobody's modules every expected to run in threads, and it was built on MS Posix API's which are poor man's abstractions of win32 api, which is itself a sometimes poor abstraction of the NT kernel ;-) And cygwin? Worse by far in implications. So 2.0 was built on top of Win32, but in a manner that's quite equivalent to the unix implementation. Yes it's single process, multi threaded, but so can unix be - so module authors must factor in the possibility. It can certainly stand improvement, optimization, tuning and even more dynamic MPM behavior. So can Unix (to a lesser extent). Yes, if you are going to use httpd/win32 for production, use 2.0 or 2.2, don't even look at 1.3, and be especially alert for some windows fixes coming down the pike in the next 2.0/2.2 releases. Bill --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|