On Jul 3, 2009, at 10:58, Gwynne Raskind wrote:
On Jul 3, 2009, at 11:39 AM, Ryan Schmidt wrote:
On http://www.php.net/manual/en/migration53.sapi.php it says of
PHP 5.3 that "FastCGI is now always enabled and can not be
disabled. See sapi/cgi/CHANGES for more details." The same text
appears in the NEWS file. In sapi/cgi/CHANGES it says "Now fastcgi
is always enabled".
[snip]
So I believe the statement "FastCGI is now always enabled" is
false, because FastCGI is not enabled if you request an Apache
SAPI. And I believe the statement that it "can not be disabled" is
false, because the --disable-cgi configure argument does disable
it. I believe the correct documentation of PHP 5.3's capabilities
would be, "The FastCGI module is now built by default, but can be
disabled by using --disable-cgi".
It seems the language of the documentation is unclear. It is not
that the CGI SAPI (now called the CGI-FCGI SAPI) is always built,
in the fashion of CLI. It is, precisely, that the FastCGI support
within the CGI SAPI can no longer be turned off. However, the SAPI
selection process still procedes as it did before.
Ah, now I understand. Now you can't get a plain-CGI version anymore;
you always get a FastCGI version. But subject to the same limitations
as before about when the CGI gets built at all. That makes sense.
Thanks for the reply.
The only CGI version of PHP I've used is the FastCGI version, so when
I think of the PHP CGI SAPI, that's what I think of, and I sometimes
forget that there is (was) another possibility. Hence when reading a
statement that "FastCGI is now always enabled", that translated in my
mind to "CGI is now always enabled" hence the confusion when I found
it not to be.
I'll see what we can do about clarifying the documentation. Sorry
for the confusion :).
I think it would be clearer if it said "FastCGI support in the CGI
SAPI is now always enabled and cannot be disabled".
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
