At 03:58 AM 12/15/2001 +0100, Tommy Finsen wrote: >I think I'll wait for a few iterations before I give it another try. >Luckily I have the HW to run PHP in CGI :). IIS5 with PHP in CGI-mode is >rock stable. Been running it for 10 months with NO downtime (except when >upgrading).
Thanks for the information. I guess I really should start testing my pages in CGI mode. I read somewhere that some functions (such as include) would slightly differently in CGI mode. I can't find a reference to it, but I remember reading that there are some really subtle differences about the way some functions interpret relative paths...or something like that. Luckily I have the HW to run PHP on Linux/Apache. :) As I clean up and redesign my site (which was completely VBScript) I'm testing each page on both my Linux development server and the Windows one. Hopefully by the time I'm done I can get everything moved over to PHP and there won't be any need to run the site on Windows at all. Just in case I'm not able to pull that off, let me ask the list another question. The site that I'm working on doesn't have that much PHP in it, except for a few pages where my users search a database and page through some results. There is no super complicated program logic involved, no INSERTS or UPDATES, just SELECTS. The live web server is a dual P3-500/256 MB RAM (it's an IBM Netfinity 5000). Let's say that I do run PHP in CGI mode on NT/IIS 4.0. In your experience (and the experience of those reading this list), under modest load do you think that human beings (i.e. my end users) will really be able to tell that it's slower than the same set of pages running on ASP/VBScript? I know that it WILL be slower, but so much so that it's obvious? Guess I could just give it a shot and see, but I'd kinda like to know what I can expect... -- 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]
