The CGI (.exe) version will not scale up well for a busy server.
Each time a page is requested, PHP.EXE is fired up, does its thing, and
In the ISAPI model, PHP is a DLL that gets glomned on to IIS, and is just
always there.

Alas, many of the third-party DLLs are not yet thread-safe, so you can't
safely *USE* ISAPI without extensive testing to be sure all the DLLs you
need will work in ISAPI mode. (They're fine in CGI mode since a separate
PHP.EXE runs for each script.)

If your site is "fast enough" leave it alone -- If not, switch to ISAPI and
test like crazy.

Oh.  There are, like, four or five things you can't do with CGI: ( and brethern will often suffice,
but they don't work on all Windoze either...)

HTTP Authentication in PHP (You can use, err, whatever IIS does for that)

Some esoteric function nobody needs anyway.

Some fourth thing that's fairly common, not real critical, and I can't

WARNING [EMAIL PROTECTED] address is an endangered species -- Use
Wanna help me out?  Like Music?  Buy a CD:
Volunteer a little time:
----- Original Message -----
From: Pete Hawkes <[EMAIL PROTECTED]>
Newsgroups: php.general
Sent: Monday, September 17, 2001 2:20 PM
Subject: Server API - what is the difference please?

> Hello,
> Sorry to bother you, I have just installed PHP4 because I am just starting
> to learn the language.
> I ran the .exe file from a Flash book CD ROM, version 4.0.4pl1. What is
> difference between the CGI and the ISAPI installation?
> I am running Windows 98SE with PWS, does the fact that my installation is
> CGI Server API effect any thing at all?
> So far everything seems to be OK including connecting to MySQL. If I have
> done something wrong please let me know.
> Many thanks
> Pete

PHP General Mailing List (
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