Author: stevehay Date: Thu Jun 18 21:49:06 2015 New Revision: 1686322 URL: http://svn.apache.org/r1686322 Log: Manually replicate r1682385 and r1686320 from https://svn.apache.org/repos/asf/perl/modperl/docs/trunk
The latter is urgently required (to update http://perl.apache.org/download/index.html) for the announcement of the release of mod_perl 2.0.9. This is quicker than regenerating the whole of https://svn.apache.org/repos/asf/perl/site, especially when using a machine that doesn't have all the necessary tools already set up. I will do a full regeneration in due course, but this will suffice for now. Modified: perl/site/docs/2.0/user/config/config.html perl/site/docs/2.0/user/design/design.html perl/site/docs/2.0/user/handlers/protocols.html perl/site/download/index.html Modified: perl/site/docs/2.0/user/config/config.html URL: http://svn.apache.org/viewvc/perl/site/docs/2.0/user/config/config.html?rev=1686322&r1=1686321&r2=1686322&view=diff ============================================================================== --- perl/site/docs/2.0/user/config/config.html (original) +++ perl/site/docs/2.0/user/config/config.html Thu Jun 18 21:49:06 2015 @@ -983,9 +983,6 @@ <li> <a name="toc_C_PerlInterpMaxRequests_"></a><a href="#C_PerlInterpMaxRequests_"><code>PerlInterpMaxRequests</code></a> </li> - <li> - <a name="toc_C_PerlInterpScope_"></a><a href="#C_PerlInterpScope_"><code>PerlInterpScope</code></a> - </li> </ul> </li> @@ -2252,49 +2249,6 @@ a fresh clone.</p> </div> <div class="index-section"> <!-- SwishCommand index --> - <h2><a name="C_PerlInterpScope_"></a><a href="#toc_C_PerlInterpScope_"><code>PerlInterpScope</code></a></h2> - -<p>As mentioned, when a request in a threaded mpm is handled by mod_perl, -an interpreter must be pulled from the interpreter pool. The -interpreter is then only available to the thread that selected it, -until it is released back into the interpreter pool. By default, an -interpreter will be held for the lifetime of the request, equivalent -to this configuration:</p> -<pre class="pre-section"> PerlInterpScope request</pre> -<p>For example, if a <code>PerlAccessHandler</code> is configured, an interpreter -will be selected before it is run and not released until after the -logging phase.</p> -<p>Interpreters will be shared across sub-requests by default, however, it -is possible to configure the interpreter scope to be per-sub-request on -a per-directory basis:</p> -<pre class="pre-section"> PerlInterpScope subrequest</pre> -<p>With this configuration, an autoindex generated page, for example, -would select an interpreter for each item in the listing that is -configured with a Perl*Handler.</p> -<p>It is also possible to configure the scope to be per-handler:</p> -<pre class="pre-section"> PerlInterpScope handler</pre> -<p>For example if <code>PerlAccessHandler</code> is configured, an interpreter will -be selected before running the handler, and put back immediately -afterwards, before Apache moves onto the next phase. If a -<code>PerlFixupHandler</code> is configured further down the chain, another -interpreter will be selected and again put back afterwards, before -<code>PerlResponseHandler</code> is run.</p> -<p>For protocol handlers, the interpreter is held for the lifetime of the -connection. However, a C protocol module might hook into mod_perl -(e.g. mod_ftp) and provide a <code>request_rec</code> record. In this case, the -default scope is that of the request. Should a mod_perl handler want -to maintain state for the lifetime of an ftp connection, it is -possible to do so on a per-virtualhost basis:</p> -<pre class="pre-section"> PerlInterpScope connection</pre> -<p>Default value: <code>request</code></p> -<p>See also: <a href="#mod_perl_Directives_Argument_Types_and_Allowed_Location">this directive argument types and allowed location</a>.</p> -<br><br> -<a href="#top" class="noPrint"><img src="../../../../images/nav/page_top.gif" width="48" height="16" border="0" alt="TOP"></a> - <br><br> - <!-- SwishCommand noindex --> - </div> - <div class="index-section"> - <!-- SwishCommand index --> <h1><a name="Debug_Directives"></a><a href="#toc_Debug_Directives">Debug Directives</a></h1> <br><br> @@ -2409,8 +2363,7 @@ arguments they expect:</p> PerlInterpMax TAKE1 SRV PerlInterpMinSpare TAKE1 SRV PerlInterpMaxSpare TAKE1 SRV - PerlInterpMaxRequests TAKE1 SRV - PerlInterpScope TAKE1 DIR</pre> + PerlInterpMaxRequests TAKE1 SRV</pre> <p>mod_perl 1.0 back-compatibility directives:</p> <pre class="pre-section"> Directive Arguments Scope -------------------------------------------- @@ -2710,4 +2663,4 @@ Changes file.</p> </div> </body> -</html> \ No newline at end of file +</html> Modified: perl/site/docs/2.0/user/design/design.html URL: http://svn.apache.org/viewvc/perl/site/docs/2.0/user/design/design.html?rev=1686322&r1=1686321&r2=1686322&view=diff ============================================================================== --- perl/site/docs/2.0/user/design/design.html (original) +++ perl/site/docs/2.0/user/design/design.html Thu Jun 18 21:49:06 2015 @@ -968,40 +968,6 @@ as those in use become available</p> interpreter is destroyed when the number is reached and replaced with a fresh one.</p> </li> -<li><a name="item_PerlInterpScope"></a><b>PerlInterpScope</b> -<p>As mentioned, when a request in a threaded mpm is handled by mod_perl, -an interpreter must be pulled from the interpreter pool. The -interpreter is then only available to the thread that selected it, -until it is released back into the interpreter pool. By default, an -interpreter will be held for the lifetime of the request, equivalent -to this configuration:</p> -<pre class="pre-section"> PerlInterpScope request</pre> -<p>For example, if a <code>PerlAccessHandler</code> is configured, an interpreter -will be selected before it is run and not released until after the -logging phase.</p> -<p>Intepreters will be shared across subrequests by default, however, it -is possible to configure the intepreter scope to be per-subrequest on -a per-directory basis:</p> -<pre class="pre-section"> PerlInterpScope subrequest</pre> -<p>With this configuration, an autoindex generated page for example would -select an interpreter for each item in the listing that is configured -with a Perl*Handler.</p> -<p>It is also possible to configure the scope to be per-handler:</p> -<pre class="pre-section"> PerlInterpScope handler</pre> -<p>With this configuration, an interpreter will be selected before -<code>PerlAccessHandlers</code> are run, and putback immediately afterwards, -before Apache moves onto the authentication phase. If a -<code>PerlFixupHandler</code> is configured further down the chain, another -interpreter will be selected and again putback afterwards, before -<code>PerlResponseHandler</code> is run.</p> -<p>For protocol handlers, the interpreter is held for the lifetime of the -connection. However, a C protocol module might hook into mod_perl -(e.g. mod_ftp) and provide a <code>request_rec</code> record. In this case, the -default scope is that of the request. Should a mod_perl handler want -to maintain state for the lifetime of an ftp connection, it is -possible to do so on a per-virtualhost basis:</p> -<pre class="pre-section"> PerlInterpScope connection</pre> -</li> </ul> <br><br> <a href="#top" class="noPrint"><img src="../../../../images/nav/page_top.gif" width="48" height="16" border="0" alt="TOP"></a> @@ -1576,4 +1542,4 @@ Changes file.</p> </div> </body> -</html> \ No newline at end of file +</html> Modified: perl/site/docs/2.0/user/handlers/protocols.html URL: http://svn.apache.org/viewvc/perl/site/docs/2.0/user/handlers/protocols.html?rev=1686322&r1=1686321&r2=1686322&view=diff ============================================================================== --- perl/site/docs/2.0/user/handlers/protocols.html (original) +++ perl/site/docs/2.0/user/handlers/protocols.html Thu Jun 18 21:49:06 2015 @@ -880,22 +880,6 @@ soon as possible and insert filters if n this phase to setup the connection record based on the type of connection that is being used. mod_perl itself uses this phase to register the connection input and output filters.</p> -<p>In mod_perl 1.0 during code development <code>Apache::Reload</code> was used to -automatically reload modified since the last request Perl modules. It -was invoked during <code>post_read_request</code>, the first HTTP request's -phase. In mod_perl 2.0 <i>pre_connection</i> is the earliest phase, so if -we want to make sure that all modified Perl modules are reloaded for -any protocols and its phases, it's the best to set the scope of the -Perl interpreter to the lifetime of the connection via:</p> -<pre class="pre-section"> PerlInterpScope connection</pre> -<p>and invoke the <code>Apache2::Reload</code> handler during the <i>pre_connection</i> -phase. However this development-time advantage can become a -disadvantage in production--for example if a connection, handled by -HTTP protocol, is configured as <code>KeepAlive</code> and there are several -requests coming on the same connection and only one handled by -mod_perl and the others by the default images handler, the Perl -interpreter won't be available to other threads while the images are -being served.</p> <p>This phase is of type <code><a href="../../../../docs/2.0/user/handlers/intro.html#item_RUN_ALL">RUN_ALL</a></code>.</p> <p>The handler's configuration scope is @@ -1732,4 +1716,4 @@ Changes file.</p> </div> </body> -</html> \ No newline at end of file +</html> Modified: perl/site/download/index.html URL: http://svn.apache.org/viewvc/perl/site/download/index.html?rev=1686322&r1=1686321&r2=1686322&view=diff ============================================================================== --- perl/site/download/index.html (original) +++ perl/site/download/index.html Thu Jun 18 21:49:06 2015 @@ -770,18 +770,18 @@ <p>Current releases:</p> <ul> - <li>mod_perl 2.0: Version 2.0.8 - April 17, 2013<br> - For use with Apache 2.0.x / 2.2.x <br/> - <a href="http://www.apache.org/dyn/closer.cgi/perl/mod_perl-2.0.8.tar.gz";>Download</a> + <li>mod_perl 2.0: Version 2.0.9 - June 18, 2015<br> + For use with Apache 2.0.x / 2.2.x / 2.4.x <br/> + <a href="http://www.apache.org/dyn/closer.cgi/perl/mod_perl-2.0.9.tar.gz";>Download</a> [ - <a href="http://www.apache.org/dist/perl/mod_perl-2.0.8.tar.gz.asc";>PGP</a> + <a href="http://www.apache.org/dist/perl/mod_perl-2.0.9.tar.gz.asc";>PGP</a> ] [ - <a href="http://www.apache.org/dist/perl/mod_perl-2.0.8.tar.gz.md5";>MD5</a> + <a href="http://www.apache.org/dist/perl/mod_perl-2.0.9.tar.gz.md5";>MD5</a> ] [ - <a href="http://www.apache.org/dist/perl/mod_perl-2.0.8.tar.gz.sha1";>SHA1</a> + <a href="http://www.apache.org/dist/perl/mod_perl-2.0.9.tar.gz.sha1";>SHA1</a> ] | - <a href="http://svn.apache.org/repos/asf/perl/modperl/tags/2_0_8";>Browse</a> | - <a href="http://svn.apache.org/repos/asf/perl/modperl/tags/2_0_8/Changes";>Changes</a> | + <a href="http://svn.apache.org/repos/asf/perl/modperl/tags/2_0_9";>Browse</a> | + <a href="http://svn.apache.org/repos/asf/perl/modperl/tags/2_0_9/Changes";>Changes</a> | <a href="../docs/2.0/user/install/install.html">Installation</a> </li> @@ -818,13 +818,13 @@ <pre> % pgpk -a KEYS - % pgpv mod_perl-2.0.8.tar.gz.asc + % pgpv mod_perl-2.0.9.tar.gz.asc <i>or</i>, % pgp -ka KEYS - % pgp mod_perl-2.0.8.tar.gz.asc + % pgp mod_perl-2.0.9.tar.gz.asc <i>or</i>, % gpg --import KEYS - % gpg --verify mod_perl-2.0.8.tar.gz.asc + % gpg --verify mod_perl-2.0.9.tar.gz.asc </pre> Alternatively, you can verify the MD5 signature on the files. A unix @@ -908,4 +908,4 @@ locally for easier reading, or to submit </body> -</html> \ No newline at end of file +</html>
