stas 2002/12/03 19:00:33
Modified: src/docs/2.0/user/handlers http.pod
src/docs/2.0/user/troubleshooting troubleshooting.pod
Log:
internal links sync
Revision Changes Path
1.7 +2 -2 modperl-docs/src/docs/2.0/user/handlers/http.pod
Index: http.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/handlers/http.pod,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- http.pod 29 Nov 2002 04:52:17 -0000 1.6
+++ http.pod 4 Dec 2002 03:00:33 -0000 1.7
@@ -959,8 +959,8 @@
</Location>
C<SetHandler> set to
-C<L<perl-script|docs::2.0::user::config::config/perl_script>> or
-C<L<modperl|docs::2.0::user::config::config/modperl>> tells Apache
+C<L<perl-script|docs::2.0::user::config::config/C_perl_script_>> or
+C<L<modperl|docs::2.0::user::config::config/C_modperl_>> tells Apache
that mod_perl is going to handle the response
generation. C<PerlResponseHandler> tells mod_perl which callback is
going to do the job.
1.4 +6 -5
modperl-docs/src/docs/2.0/user/troubleshooting/troubleshooting.pod
Index: troubleshooting.pod
===================================================================
RCS file:
/home/cvs/modperl-docs/src/docs/2.0/user/troubleshooting/troubleshooting.pod,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- troubleshooting.pod 29 Nov 2002 07:20:22 -0000 1.3
+++ troubleshooting.pod 4 Dec 2002 03:00:33 -0000 1.4
@@ -53,16 +53,17 @@
The issue is that the C array C<environ[]> is not thread-safe.
Therefore mod_perl 2.0 unties C<%ENV> from the underlying C<environ[]>
array under the
-I<L<perl-script|docs::2.0::user::config::config/perl_script>> handler.
+I<L<perl-script|docs::2.0::user::config::config/C_perl_script_>>
+handler.
The C<DBD::Oracle> driver or client library uses C<getenv()> (which
fetches from the C<environ[]> array). When C<%ENV> is untied from
C<environ[]>, Perl code will see C<%ENV> changes, but C code will not.
-The I<L<modperl|docs::2.0::user::config::config/modperl>> handler does
-not untie C<%ENV> from C<environ[]>. Still one should avoid setting
-C<%ENV> values whenever possible. And if it is required, should be
-done at startup time.
+The I<L<modperl|docs::2.0::user::config::config/C_modperl_>> handler
+does not untie C<%ENV> from C<environ[]>. Still one should avoid
+setting C<%ENV> values whenever possible. And if it is required,
+should be done at startup time.
In the particular case of the C<DBD::> drivers, you can set the
variables that don't change (C<$ENV{ORACLE_HOME}> and
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
