Linked by Thom Holwerda on Thu 30th Jul 2009 16:06 UTC, submitted by estherschindler
General Development Windows might be a popular platform for running certain kinds of Web applications. But too many developers have been burnt by trying to deploy PHP applications on a Windows server. "If you banged on [a PHP application] too hard on Windows, IIS would crash, and nobody could tell why it died," Microsoft's Garrett Serack says. Microsoft is aiming to change that. In fact, while you weren't looking, they already made some improvements.
E-mail Print r 1   8 Comment(s)
Thread beginning with comment 376269
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

RTFA, they barely talked about IIS, more about the build process for windows, and the external libraries used.

What does that statement have to do with the question he asked? Nothing.

Yes, PHP runs happily on Apache for Windows. No need to use IIS, unless your company is a Microsoft partner/Microsoft certified org/Windows certified or whatever - then you're probably tied to IIS to keep the accreditation (guessing - correct me if I am wrong.)

Reply Parent Score: 3

google_ninja Member since:

Why was he asking questions about iis when it was only mentioned once in a two page article about improving the performance of php on windows?

Reply Parent Score: 0

Johann Chua Member since:

Because apparently it's a problem with running PHP with IIS, not running PHP on Windows per se. You don't have to use IIS as the webserver under Windows, unless you need ASP and the like.

Reply Parent Score: 4

segedunum Member since:

Because what they mean by running PHP on 'Windows' is clearly Windows + IIS. If you run PHP on Windows under Apache then most, if not all, of those issues disappear. Thus, running PHP on Windows is not a problem at all. They just chose to ignore the most obvious solution.

Edited 2009-08-01 23:26 UTC

Reply Parent Score: 2