The only reason I am aware of to use PHP as a CGI is on Windows. Both apache
and the php module for windows apache is considered "beta quality", so most
people don't want to install beta software on their production machine.
But just on my local system I've never had a problem with PHP as CGI. I
honestly thought I had PHP as a module until I re-read my phpinfo, lol. And
I assumed that NuSphere would install it as a module...;)
--
Plutarck
Should be working on something...
...but forgot what it was.
"Franklin Hays" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
> RE: PHP as a CGI or Module
>
> This has been discussed some but I am interested to see if one is more
> popular then the other. My experience has been most people run PHP as a
> apache module but is there a specific benefit to run it as a cgi
> program? What about very large servers such as web hosts? I am currently
> wrestling with some issues (apaches global variables) that aren't working
> with php -cgi and wonder if this is a common occurance with php-cgi or
> just a misconfiguration on the hosts end. Does one version serve the
> pages faster or provide less overhead on the server?
>
> I have read a few FAQ's on this but interested to see what is happening in
> the real world. Is one form more popular then the other?
>
> //frank
>
>
> --
> PHP General 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 General 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]
