cvs commit: modperl-docs/src/docs/general/os/win32 faq.pod
randyk 2004/03/02 19:58:18 Modified:src/docs/general/os/win32 faq.pod Log: add note about slowness of Apache::Log on Win32. Revision ChangesPath 1.13 +7 -0 modperl-docs/src/docs/general/os/win32/faq.pod Index: faq.pod === RCS file: /home/cvs/modperl-docs/src/docs/general/os/win32/faq.pod,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- faq.pod 31 Dec 2003 19:03:07 - 1.12 +++ faq.pod 3 Mar 2004 03:58:18 - 1.13 @@ -298,6 +298,13 @@ to be used within the Apache2 sources are missing. Nevertheless, they may be useful for building and installing 3rd-party C modules. +=head2 Why is use of CApache::Log on Win32 so slow? + +On Win32 Apache attempts to lock all writes to a file whenever +it's opened for append (which is the case with logging functions), as +Unix has this behavior built-in, while Win32 does not. Therefore +CApache::Log functions could be slower than Perl's print()/warn(). + =head1 Maintainers Maintainer is the person(s) you should contact with updates, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/2.0/api/Apache Filter.pod
stas2004/03/03 13:12:27 Modified:src/docs/2.0/api/Apache Filter.pod Log: more updates on the issue with add filter Revision ChangesPath 1.11 +7 -1 modperl-docs/src/docs/2.0/api/Apache/Filter.pod Index: Filter.pod === RCS file: /home/cvs/modperl-docs/src/docs/2.0/api/Apache/Filter.pod,v retrieving revision 1.10 retrieving revision 1.11 diff -u -u -r1.10 -r1.11 --- Filter.pod3 Mar 2004 21:07:53 - 1.10 +++ Filter.pod3 Mar 2004 21:12:27 - 1.11 @@ -547,12 +547,18 @@ =back -META: It seems that you can't add a filter when another filter is +[META: It seems that you can't add a filter when another filter is called. I've tried to add an output connection filter from the input connection filter when it was called for the first time. It didn't have any affect for the first request (over keepalive connection). The only way I succeeded to do that is from that input connection filter's filter_init handler. +In fact it does work if there is any filter additional filter of the +same kind configured from httpd.conf or via filter_init. It looks like +there is a bug in httpd, where it doesn't prepare the chain of 3rd +party filter if none were inserted before the first filter was called.] + + =head2 Cadd_output_filter - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/2.0/user/porting compat.pod
stas2004/03/03 15:33:53
Modified:src/docs/2.0/api/ModPerl Registry.pod
src/docs/2.0/user/coding coding.pod
src/docs/2.0/user/install install.pod
src/docs/2.0/user/porting compat.pod
Log:
$ENV{GATEWAY_INTERFACE} is no longer special
Revision ChangesPath
1.4 +0 -2 modperl-docs/src/docs/2.0/api/ModPerl/Registry.pod
Index: Registry.pod
===
RCS file: /home/cvs/modperl-docs/src/docs/2.0/api/ModPerl/Registry.pod,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -u -r1.3 -r1.4
--- Registry.pod 6 Jun 2003 03:11:55 - 1.3
+++ Registry.pod 3 Mar 2004 23:33:52 - 1.4
@@ -71,8 +71,6 @@
The Apache function `exit' overrides the Perl core built-in function.
-The environment variable BGATEWAY_INTERFACE is set to CCGI-Perl/1.1.
-
=head1 Commandline Switches In First Line
Normally when a Perl script is run from the command line or under CGI,
1.31 +2 -6 modperl-docs/src/docs/2.0/user/coding/coding.pod
Index: coding.pod
===
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/coding/coding.pod,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -u -r1.30 -r1.31
--- coding.pod2 Mar 2004 21:05:32 - 1.30
+++ coding.pod3 Mar 2004 23:33:52 - 1.31
@@ -72,12 +72,6 @@
use constant MP2 = ($mod_perl::VERSION = 1.99);
# die I want mod_perl 2.0! unless MP2;
-=item *
-
-C$ENV{GATEWAY_INTERFACE} - is set to CCGI-Perl/1.1 for
-compatibility with mod_perl 1.0. This variable is deprecated in
-mod_perl 2.0. Use C$ENV{MOD_PERL} instead.
-
=back
mod_perl passes (exports) the following shell environment variables
@@ -290,6 +284,8 @@
CL$r-Egtassbackwards|docs::2.0::api::Apache::RequestRec/C_assbackwards_
method. Notice that registry handlers will do that for you if the
script's name start with the Cnph- prefix.
+
+
=head3 Forcing HTTP Response Headers Out
1.52 +0 -15 modperl-docs/src/docs/2.0/user/install/install.pod
Index: install.pod
===
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/install/install.pod,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -u -r1.51 -r1.52
--- install.pod 19 Jan 2004 20:04:32 - 1.51
+++ install.pod 3 Mar 2004 23:33:53 - 1.52
@@ -410,21 +410,6 @@
=item *
-Environment variable CGATEWAY_INTERFACE will be enabled only if
-CPerlOptions +SetupEnv is enabled and its value would be the
-default:
-
- CGI/1.1
-
-and not:
-
- CGI-Perl/1.1
-
-The use of C$ENV{GATEWAY_INTERFACE} is deprecated and the existance
-of C$ENV{MOD_PERL} should be checked instead.
-
-=item *
-
Deprecated special variable, C$Apache::__T won't be available. Use
C${^TAINT} instead.
1.43 +12 -6 modperl-docs/src/docs/2.0/user/porting/compat.pod
Index: compat.pod
===
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/porting/compat.pod,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -u -r1.42 -r1.43
--- compat.pod24 Feb 2004 02:22:28 - 1.42
+++ compat.pod3 Mar 2004 23:33:53 - 1.43
@@ -401,15 +401,21 @@
=head2 C$ENV{GATEWAY_INTERFACE}
-The environment variable C$ENV{GATEWAY_INTERFACE} is deprecated in
-mod_perl 2.0 (See:
-CLMP_COMPAT_1X=0|docs::2.0::user::install::install/MP_COMPAT_1X). Instead
-use C$ENV{MOD_PERL} (available in both mod_perl generations), which
-is set to something like this:
+The environment variable C$ENV{GATEWAY_INTERFACE} is not special in
+mod_perl 2.0, but the same as any other CGI environment variables.
+
+Instead use C$ENV{MOD_PERL} (available in both mod_perl
+generations), which is set to the mod_perl version, like so:
mod_perl/1.99_03-dev
-However to check the version it's better to use C$mod_perl::VERSION:
+Therefore in order to check whether you are running under mod_perl,
+you'd say:
+
+ if ($ENV{MOD_PERL}) { ... }
+
+To check for a specific version it's better to use
+C$mod_perl::VERSION:
use mod_perl;
use constant MP2 = ($mod_perl::VERSION = 1.99);
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cvs commit: modperl-docs/src/docs/2.0/user/porting compat.pod
stas2004/03/03 15:37:20
Modified:src/docs/2.0/user/porting compat.pod
Log:
a better explanation
Revision ChangesPath
1.44 +10 -1 modperl-docs/src/docs/2.0/user/porting/compat.pod
Index: compat.pod
===
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/porting/compat.pod,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -u -r1.43 -r1.44
--- compat.pod3 Mar 2004 23:33:53 - 1.43
+++ compat.pod3 Mar 2004 23:37:20 - 1.44
@@ -402,7 +402,16 @@
=head2 C$ENV{GATEWAY_INTERFACE}
The environment variable C$ENV{GATEWAY_INTERFACE} is not special in
-mod_perl 2.0, but the same as any other CGI environment variables.
+mod_perl 2.0, but the same as any other CGI environment variables,
+i.e. it'll be enabled only if CLPerlOptions
++SetupEnv|docs::2.0::user::config::config/C_SetupEnv_ is enabled and
+its value would be the default:
+
+ CGI/1.1
+
+or anything else Apache decides to set it to, but not:
+
+ CGI-Perl/1.1
Instead use C$ENV{MOD_PERL} (available in both mod_perl
generations), which is set to the mod_perl version, like so:
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
