For what it's worth, I have been running PHP ISAPI (versions 4.0.6 and
earlier) on Win2k and WinNT4 (SP6) for quite a while - 12 months and approx
2 years, respectively, and have had not a single problem - totally
fault-free.  I have to say that I am not using IIS though - these machines
are running Sambar server, version 5 (It's free, and I can highly recommend
it! - http://www.sambar.com).  I have upgraded the WinNT machine to PHP
4.1.0, and so far, there have been no problems, all seems fine, but it is
only a few days ...!

Jeff Waldock

-----Original Message-----
From: Michael Sims [mailto:[EMAIL PROTECTED]]
Sent: 15 December 2001 02:25
To: Flint Doungchak; [EMAIL PROTECTED]
Subject: Re: [PHP-WIN] ISAPI Status


At 12:27 PM 12/14/2001 -0800, Flint Doungchak wrote:
>I was just wanting to see what people are experiencing with the ISAPI
module
>for IIS 5.0 with PHP 4.1.0.

Sorry I don't have an answer to your question, but just a related question
of my own.  I've seen lots of people refer to 4.1.0 as "finally a stable
ISAPI dll".  Are people having that much trouble with the previous
versions?  I don't have a lot of experience running PHP on Windows, but I
have been toying with 4.0.6 as an ISAPI dll running on NT/IIS 4.0 for about
three weeks now.  It's done some funky things, usually right after I start
the server, but if I manage to get it started it seems to stay running.

I'm just wondering if my experience is common or not...right now I don't
have a super compelling reason to immediately upgrade because 4.0.6 is
pretty solid for me...

Of course, I'm just doing development on this machine, and it's only me and
about three other people who hit it regularly.  Should I be expecting it to
explode when I start putting it into production?



--
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]


-- 
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]

Reply via email to