Remove info about SAPIs which are removed as of PHP 7.0.0

git-svn-id: https://svn.php.net/repository/phpdoc/en/trunk@350661 c90b9560-bf6c-de11-be94-00142212c4b1
This commit is contained in:
Christoph Michael Becker 2020-09-26 16:56:25 +00:00
parent 90d1590c14
commit e443388d42
9 changed files with 15 additions and 131 deletions

View file

@ -7,16 +7,6 @@
Application Programming Interface</literal>) for PHP.
</para>
<variablelist>
<varlistentry xml:id="configure.with-aolserver">
<term>
<option role="configure">--with-aolserver=DIR</option>
</term>
<listitem>
<para>
Specify path to the installed AOLserver.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-apxs">
<term>
<option role="configure">--with-apxs[=FILE]</option>
@ -63,18 +53,6 @@
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-caudium">
<term>
<option role="configure">--with-caudium=DIR</option>
</term>
<listitem>
<para>
Build PHP as a Pike module for use with Caudium. DIR is the Caudium server
dir, with the default value <filename>/usr/local/caudium/server</filename>.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.disable-cli">
<term>
<option role="configure">--disable-cli</option>
@ -113,16 +91,6 @@
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-isapi">
<term>
<option role="configure">--with-isapi=DIR</option>
</term>
<listitem>
<para>
Build PHP as an ISAPI module for use with Zeus.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-nsapi">
<term>
<option role="configure">--with-nsapi=DIR</option>
@ -133,47 +101,6 @@
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-phttpd">
<term>
<option role="configure">--with-phttpd=DIR</option>
</term>
<listitem>
<para>
No information yet.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-pi3web">
<term>
<option role="configure">--with-pi3web=DIR</option>
</term>
<listitem>
<para>
Build PHP as a module for use with Pi3Web.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-roxen">
<term>
<option role="configure">--with-roxen=DIR</option>
</term>
<listitem>
<para>
Build PHP as a Pike module. DIR is the base Roxen directory, normally
<filename>/usr/local/roxen/server</filename>.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.enable-roxen-zts">
<term>
<option role="configure">--enable-roxen-zts</option>
</term>
<listitem>
<para>
Build the Roxen module using Zend Thread Safety.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-servlet">
<term>
<option role="configure">--with-servlet[=DIR]</option>
@ -185,38 +112,6 @@
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-thttpd">
<term>
<option role="configure">--with-thttpd=SRCDIR</option>
</term>
<listitem>
<para>
Build PHP as thttpd module.
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-tux">
<term>
<option role="configure">--with-tux=MODULEDIR</option>
</term>
<listitem>
<para>
Build PHP as a TUX module (Linux only).
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.with-webjames">
<term>
<option role="configure">--with-webjames=SRCDIR</option>
</term>
<listitem>
<para>
Build PHP as a WebJames module (RISC OS only)
</para>
</listitem>
</varlistentry>
<varlistentry xml:id="configure.disable-cgi">
<term>

View file

@ -313,8 +313,8 @@ foreach ($headers as $name => $content) {
to create a plain HTML file (not parsed by PHP) as the entry page
into an authenticated directory. Then use a META tag to redirect
to the PHP page, or have a link to the PHP page. PHP will
then recognize the authentication correctly. With the ISAPI
module, this is not a problem. This should not affect other
then recognize the authentication correctly.
This should not affect other
NT web servers. For more information, see:
<link xlink:href="&url.iis;">&url.iis;</link> and the manual
section on <link linkend="features.http-auth">HTTP Authentication

View file

@ -55,7 +55,7 @@
</simpara>
<simpara>
The last method is to use PHP as a plug-in for a multithreaded web
server. Currently PHP 4 has support for ISAPI, WSAPI, and NSAPI (on
server. Currently PHP has support for WSAPI, and NSAPI (on
Windows), which all allow PHP to be used as a plug-in on multithreaded
servers like Netscape FastTrack (iPlanet), Microsoft's Internet Information
Server (IIS), and O'Reilly's WebSite Pro. The behavior is essentially

View file

@ -20,8 +20,7 @@
<simpara>
SAPI module specific location (<literal>PHPIniDir</literal> directive
in Apache 2, <literal>-c</literal> command line option in CGI and CLI,
<literal>php_ini</literal> parameter in NSAPI,
<literal>PHP_INI_PATH</literal> environment variable in THTTPD)
<literal>php_ini</literal> parameter in NSAPI)
</simpara>
</listitem>
<listitem>

View file

@ -31,9 +31,8 @@
server. For many servers PHP has a direct module
interface (also called SAPI). These servers include
Apache, Microsoft Internet Information Server,
Netscape and iPlanet servers. Many other servers
have support for ISAPI, the Microsoft module
interface (OmniHTTPd for example). If PHP has no
Netscape and iPlanet servers.
If PHP has no
module support for your web server, you can always
use it as a CGI or FastCGI processor. This means you set up
your server to use the CGI executable of

View file

@ -295,13 +295,6 @@
Set to a non-empty value if the script was queried through the HTTPS
protocol.
</simpara>
<note>
<simpara>
Note that when using ISAPI with IIS, the value will be
<literal>off</literal> if the request was not made through the HTTPS
protocol.
</simpara>
</note>
</listitem>
</varlistentry>

View file

@ -35,7 +35,7 @@
so two concurrent web server processes modifying the same dBase file would
have very likely ruined your database. This can happen even with dbase
7.0.0+ on systems which implement the locks at the process level with
multithreaded SAPIs such as ISAPI.
multithreaded SAPIs.
</para>
</caution>
<para>

View file

@ -179,7 +179,7 @@ fclose($fp);
<warning>
<para>
On some operating systems <function>flock</function> is implemented at
the process level. When using a multithreaded server API like ISAPI you
the process level. When using a multithreaded server API you
may not be able to rely on <function>flock</function> to protect files
against other PHP scripts running in parallel threads of the same server
instance!

View file

@ -28,15 +28,13 @@
</para>
<para>
Although not exhaustive, the possible return values include
<literal>aolserver</literal>, <literal>apache</literal>,
<literal>apache2filter</literal>, <literal>apache2handler</literal>,
<literal>caudium</literal>, <literal>cgi</literal> (until PHP 5.3),
<literal>apache</literal>,
<literal>apache2handler</literal>,
<literal>cgi</literal> (until PHP 5.3),
<literal>cgi-fcgi</literal>, <literal>cli</literal>, <literal>cli-server</literal>,
<literal>continuity</literal>, <literal>embed</literal>, <literal>fpm-fcgi</literal>,
<literal>isapi</literal>, <literal>litespeed</literal>,
<literal>milter</literal>, <literal>nsapi</literal>, <literal>phpdbg</literal>,
<literal>phttpd</literal>, <literal>pi3web</literal>, <literal>roxen</literal>,
<literal>thttpd</literal>, <literal>tux</literal>, and <literal>webjames</literal>.
<literal>embed</literal>, <literal>fpm-fcgi</literal>,
<literal>litespeed</literal>,
<literal>nsapi</literal>, <literal>phpdbg</literal>.
</para>
</refsect1>
@ -79,7 +77,7 @@ if (substr($sapi_type, 0, 3) == 'cgi') {
<para>
The defined <acronym>SAPI</acronym> may not be obvious, because for
example instead of <literal>apache</literal> it may be defined as
<literal>apache2handler</literal> or <literal>apache2filter</literal>.
<literal>apache2handler</literal>.
</para>
</tip>
</refsect1>