RE: [PHP-WIN] what is the REAL deal on PHP effieciency with windo ws

While I'm not certain what you mean by CGI knockoff (maybe you mean Perl knockoff) but in Windows, PHP can be run in one of two modes: CGI or ISAPI module. Theoretically, the ISAPI module will provide much faster response times and allows for sessions. But, the CGI implementation is much more reliable (at this point). Some users have implemented PHP as BOTH a CGI application and an ISAPI module (Pablo Vera is one I think who does this). Thus using the CGI implementation when something is broken in the ISAPI module. One of the main difference between Perl and PHP as a CGI application is the ability to mix/swap HTML and PHP throughout the PHP script. The REAL DEAL is this. The ISAPI module is ever-so-slighty faster than the CGI implementation but is less stable. (I used the ISAPI module up until I started trying to hit Oracle databases with it where it started failing). You CAN use persistant database connections (such as OCIPLOGON for Oracle) in the CGI implementation and the response times are infinitely faster (since you don't have to log on to the database upon each query). In my own experience, the difference was 25-30 second response time with OCILogon (almost all of which was logging on to the database) to a 2-3 second response time with OCIPLogon. As for multi-threading, the ISAPI module 'is' thread-safe, but there are inconsistancies in the additional dlls and (from version to version) sometimes in the main module... so take that for what it is worth... On top of all that, one of the main reasons many people go to PHP is the native database connectivity. I personally hit Access, MSSQL and Oracle databases seemlessly with PHP. I'm not certain that any other scripting language has that capability. --------------------- Founder of The 'What Kind of Idiot Uses PHP with IIS with Oracle on NT?' Consortium Members: John Asendorf, Thomas Kryger, Florian Clever, Ron Woods, Bod John Asendorf - jasendorf@lcounty.com Web Applications Developer http://www.lcounty.com - NEW FEATURES ADDED DAILY! Licking County, Ohio, USA 740-349-3631 Vah! Denuone Latine loquebar? Me ineptum. Interdum modo elabitur. The benefit to the government of replacing all $1 Federal Reserve notes with $1 coins would be $522.2 million per year, according to estimates of the General Accouting Office released on April 7, 2000. > -----Original Message----- > From: Richard Weth [mailto:rick_weth@yahoo.com] > Sent: Sunday, January 07, 2001 2:33 AM > To: php-windows@lists.php.net > Subject: [PHP-WIN] what is the REAL deal on PHP effieciency > with windows > > > All > > I picked up a book on PHP about a week ago. I also have read > the FQA on www.php.net. > The book alluded to PHP being way better than CGI and it's > very clear why in Unix. PHP is > built into apache .. simple to understand. > > However things get a little hazy in the book on Windows, and > the FAQ did nothing > to help me here. For instance Cold Fusion in Windows is a > multi threaded service with > ISAPI connectivity. Very simple to relate to. > > PHP does not appear to be multi threaded according to the > FAQ? So if PHP > faster than CGI and can I have persistant "HOT" connections > to a data base? > > In other words do I fork PHP scripts in Windows (IIS 5.0) or NOT? > Also what is the technology that allows me to reuse a > persistant DB connection, > such that there is a real efficiency in terms of time/transaction. > > A pointer to doc (even in www.php.net) would be acceptable. > Or something like that. > It's just "the simple message" on PHP and Windows seems > difuse. I get the > feeling PHP will be great on Windows REAL SOON. But in the > meantime it's just > a CGI knockoff. If that assertion is wrong I want to know > why! I also think that if it's > right I don't want to spend any more time chasing the PHP > rainbow at this time. > > > > > > > > > > > > >