I was initially using ISAPI with IIS on win2k and found that it was quite
prone to crashing after about 20 or thirty hits to a php page.
I then moved to using CGI with IIS and found that it could last for a couple
of hundred hits before it crashed (PHP this is)
Finally I've moved to using the ISAPI module in Apache and have not had it
crash yet (although there haven't been more than about a thousand hits so
far). Therefore my empirical evidence suggests that IIS is not that stable
using PHP at the moment, I'm not sure who's fault it is, but they don't seem
to combine too well.
I hope that helps, it would certainly bear some testing.
Martin Kemp.
> -----Original Message-----
> From: Phil Driscoll [mailto:[EMAIL PROTECTED]]
> Sent: 06 May 2001 11:02
> To: [EMAIL PROTECTED]; steff
> Subject: Re: [PHP-WIN] Surprises with PHP4/IIS?
>
>
> >Up to now I always worked with PHP/Apache (Unix, Linux, Win; CGI,
> >Module). Now a customer of mine would like to subscribe for a PHP/IIS
> >hosting offer. What surprises, exceptions, and special cases (compared
> >to Apache solutions) do I have to take into consideration when I agree
> >with the customers proposal?
>
> The only real issue is that the ISAPI module is not stable enough for
> serious use so you will have to go with the cgi version. This
> will give you
> a bit of a performance hit and also mean that authentication headers have
> already been handled by the server before the php script gets a
> look in, so
> you can't do php authentication (although you can let NT do authentication
> for you).
>
> Cheers
> --
> Phil Driscoll
> Dial Solutions
> +44 (0)113 294 5112
> http://www.dialsolutions.com
> http://www.dtonline.org
>
>
--
PHP Windows Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
