perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From steve...@apache.org
Subject svn commit: r1682385 - in /perl/modperl/docs/trunk/src/docs/2.0/user: config/config.pod design/design.pod handlers/protocols.pod
Date Fri, 29 May 2015 07:51:56 GMT
Author: stevehay
Date: Fri May 29 07:51:56 2015
New Revision: 1682385

URL: http://svn.apache.org/r1682385
Log:
Remove documentation of PerlInterpScope, now removed from mod_perl by r1682369

Modified:
    perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod
    perl/modperl/docs/trunk/src/docs/2.0/user/design/design.pod
    perl/modperl/docs/trunk/src/docs/2.0/user/handlers/protocols.pod

Modified: perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod
URL: http://svn.apache.org/viewvc/perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod?rev=1682385&r1=1682384&r2=1682385&view=diff
==============================================================================
--- perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod (original)
+++ perl/modperl/docs/trunk/src/docs/2.0/user/config/config.pod Fri May 29 07:51:56 2015
@@ -1197,57 +1197,6 @@ See also: L<this directive argument type
 location|/mod_perl_Directives_Argument_Types_and_Allowed_Location>.
 
 
-=head2 C<PerlInterpScope>
-
-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:
-
-  PerlInterpScope request
-
-For example, if a C<PerlAccessHandler> is configured, an interpreter
-will be selected before it is run and not released until after the
-logging phase.
-
-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:
-
-  PerlInterpScope subrequest
-
-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.
-
-It is also possible to configure the scope to be per-handler:
-
-  PerlInterpScope handler
-
-For example if C<PerlAccessHandler> 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
-C<PerlFixupHandler> is configured further down the chain, another
-interpreter will be selected and again put back afterwards, before
-C<PerlResponseHandler> is run.
-
-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 C<request_rec> 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:
-
-  PerlInterpScope connection
-
-Default value: C<request>
-
-See also: L<this directive argument types and allowed
-location|/mod_perl_Directives_Argument_Types_and_Allowed_Location>.
-
-
 =head1 Debug Directives
 
 =head2 C<PerlTrace>
@@ -1375,7 +1324,6 @@ Perl Interpreter management directives:
   PerlInterpMinSpare           TAKE1      SRV
   PerlInterpMaxSpare           TAKE1      SRV
   PerlInterpMaxRequests        TAKE1      SRV
-  PerlInterpScope              TAKE1      DIR
 
 mod_perl 1.0 back-compatibility directives:
 

Modified: perl/modperl/docs/trunk/src/docs/2.0/user/design/design.pod
URL: http://svn.apache.org/viewvc/perl/modperl/docs/trunk/src/docs/2.0/user/design/design.pod?rev=1682385&r1=1682384&r2=1682385&view=diff
==============================================================================
--- perl/modperl/docs/trunk/src/docs/2.0/user/design/design.pod (original)
+++ perl/modperl/docs/trunk/src/docs/2.0/user/design/design.pod Fri May 29 07:51:56 2015
@@ -111,52 +111,6 @@ The maximum number of requests an interp
 interpreter is destroyed when the number is reached and replaced with
 a fresh one.
 
-=item PerlInterpScope
-
-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:
-
-  PerlInterpScope request
-
-For example, if a C<PerlAccessHandler> is configured, an interpreter
-will be selected before it is run and not released until after the
-logging phase.
-
-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:
-
-  PerlInterpScope subrequest
-
-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.
-
-It is also possible to configure the scope to be per-handler:
-
-  PerlInterpScope handler
-
-With this configuration, an interpreter will be selected before
-C<PerlAccessHandlers> are run, and putback immediately afterwards,
-before Apache moves onto the authentication phase.  If a
-C<PerlFixupHandler> is configured further down the chain, another
-interpreter will be selected and again putback afterwards, before
-C<PerlResponseHandler> is run.
-
-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 C<request_rec> 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:
-
-  PerlInterpScope connection
-
-
 =back
 
 =head2 TIPool

Modified: perl/modperl/docs/trunk/src/docs/2.0/user/handlers/protocols.pod
URL: http://svn.apache.org/viewvc/perl/modperl/docs/trunk/src/docs/2.0/user/handlers/protocols.pod?rev=1682385&r1=1682384&r2=1682385&view=diff
==============================================================================
--- perl/modperl/docs/trunk/src/docs/2.0/user/handlers/protocols.pod (original)
+++ perl/modperl/docs/trunk/src/docs/2.0/user/handlers/protocols.pod Fri May 29 07:51:56 2015
@@ -60,25 +60,6 @@ this phase to setup the connection recor
 connection that is being used.  mod_perl itself uses this phase to
 register the connection input and output filters.
 
-In mod_perl 1.0 during code development C<Apache::Reload> was used to
-automatically reload modified since the last request Perl modules. It
-was invoked during C<post_read_request>, the first HTTP request's
-phase. In mod_perl 2.0 I<pre_connection> 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:
-
-  PerlInterpScope connection
-
-and invoke the C<Apache2::Reload> handler during the I<pre_connection>
-phase. However this development-time advantage can become a
-disadvantage in production--for example if a connection, handled by
-HTTP protocol, is configured as C<KeepAlive> 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.
-
 This phase is of type
 C<L<RUN_ALL|docs::2.0::user::handlers::intro/item_RUN_ALL>>.
 



---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org


Mime
View raw message