pereinar 2002/06/16 05:43:39
Modified: src/start/tips handler.pod
. TODO
src/contribute cvs_howto.pod
src/contribute/docs style.pod
src/docs/2.0/api/mod_perl-2.0/Apache compat.pod
src/docs/2.0/devel/testing testing.pod
src/docs/2.0/user/design design.pod
src/docs/2.0/user/help help.pod
src/docs/2.0/user/overview overview.pod
src/docs/general multiuser.pod
src/download binaries.pod index_top.html source.pod
src/maillist email-etiquette.pod
Log:
".x" cleansing time! Ran search on "1.x" and "2.x" and removed all occurences.
Revision Changes Path
1.8 +1 -1 modperl-docs/src/start/tips/handler.pod
Index: handler.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/start/tips/handler.pod,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- handler.pod 26 Apr 2002 22:41:09 -0000 1.7
+++ handler.pod 16 Jun 2002 12:43:38 -0000 1.8
@@ -2,7 +2,7 @@
Content Handler Example
-=head1 Creating a content handler with mod_perl 1.x
+=head1 Creating a content handler with mod_perl 1.0
Handlers are simply perl subroutines called by the server at various
stages of the HTTP request cycle. A content handler is a subroutine
1.63 +0 -2 modperl-docs/TODO
Index: TODO
===================================================================
RCS file: /home/cvs/modperl-docs/TODO,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- TODO 16 Jun 2002 12:04:16 -0000 1.62
+++ TODO 16 Jun 2002 12:43:38 -0000 1.63
@@ -58,8 +58,6 @@
- Need to resolve prompt issue. (user/root prompt)
-- Replace occurences of 1.x and 2.x with 1.0 and 2.0
-
Search:
-------
- consider adding auto-focus feature:
1.2 +1 -1 modperl-docs/src/contribute/cvs_howto.pod
Index: cvs_howto.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/contribute/cvs_howto.pod,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- cvs_howto.pod 10 Jun 2002 21:35:26 -0000 1.1
+++ cvs_howto.pod 16 Jun 2002 12:43:38 -0000 1.2
@@ -327,7 +327,7 @@
=item modperl
-sources for mod_perl 1.x, for use with apache-1.3
+sources for mod_perl 1.0, for use with apache-1.3
=item apache-1.3
1.3 +5 -0 modperl-docs/src/contribute/docs/style.pod
Index: style.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/contribute/docs/style.pod,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- style.pod 16 Jun 2002 10:53:56 -0000 1.2
+++ style.pod 16 Jun 2002 12:43:38 -0000 1.3
@@ -318,6 +318,11 @@
the important changes that would be of interest to the end user. For
more info please read the L<Changes file|contribute::docs::changes_file> doc.
+=item * Naming mod_perl major versions
+
+We have adopted the convention that mod_perl major versions should be
+named as I<1.0> and I<2.0>, and not I<1.x> and I<2.x>.
+
=back
=head1 Review process
1.4 +4 -4
modperl-docs/src/docs/2.0/api/mod_perl-2.0/Apache/compat.pod
Index: compat.pod
===================================================================
RCS file:
/home/cvs/modperl-docs/src/docs/2.0/api/mod_perl-2.0/Apache/compat.pod,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- compat.pod 19 May 2002 09:40:53 -0000 1.3
+++ compat.pod 16 Jun 2002 12:43:38 -0000 1.4
@@ -1,6 +1,6 @@
=head1 NAME
-Apache::compat -- 1.x backward compatibility functions deprecated in 2.x
+Apache::compat -- 1.0 backward compatibility functions deprecated in 2.0
=head1 SYNOPSIS
@@ -8,12 +8,12 @@
=head1 DESCRIPTION
-C<Apache::compat> provides mod_perl 1.x compatibility layer.
+C<Apache::compat> provides mod_perl 1.0 compatibility layer.
It includes most of the functions that are deprecated in mod_perl
-2.x. If your code uses any of these functions you should just load
+2.0. If your code uses any of these functions you should just load
this module at the server startup, and chances are that everything
-should work as it did in 1.x.
+should work as it did in 1.0.
However, certain functionality is not optimized and therefore it's the
best to try to port your code not to use deprecated functions and stop
1.24 +3 -3 modperl-docs/src/docs/2.0/devel/testing/testing.pod
Index: testing.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/devel/testing/testing.pod,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- testing.pod 2 Jun 2002 08:11:35 -0000 1.23
+++ testing.pod 16 Jun 2002 12:43:38 -0000 1.24
@@ -99,7 +99,7 @@
% perl Makefile.PL
% make && make test && make install
-If you install mod_perl 2.x, you get C<Apache::Test> installed as
+If you install mod_perl 2.0, you get C<Apache::Test> installed as
well.
=head1 Running Tests
@@ -917,7 +917,7 @@
SetHandler modperl
-is mod_perl 2.0 configuration, if you are running under mod_perl 1.x
+is mod_perl 2.0 configuration, if you are running under mod_perl 1.0
use the appropriate setting.
As mentioned before you can use C<Apache::Reload> to automatically
@@ -1190,7 +1190,7 @@
}
1;
-[F] C<Apache::Const> is mod_perl 2.x's package, if you test under 1.x,
+[F] C<Apache::Const> is mod_perl 2.0's package, if you test under 1.0,
use the C<Apache::Constants> module instead [/F].
The configuration part for this test will be autogenerated by the
1.9 +19 -19 modperl-docs/src/docs/2.0/user/design/design.pod
Index: design.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/design/design.pod,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- design.pod 22 May 2002 12:13:44 -0000 1.8
+++ design.pod 16 Jun 2002 12:43:38 -0000 1.9
@@ -1,6 +1,6 @@
=head1 NAME
-mod_perl_design - notes on the design and goals of mod_perl-2.0
+Notes on the design and goals of mod_perl-2.0
=head1 Description
@@ -8,12 +8,12 @@
=head1 Introduction
-In version 2.0 of mod_perl, the basic concept of 1.x still applies:
+In version 2.0 of mod_perl, the basic concept of 1.0 still applies:
Provide complete access to the Apache C API
via the Perl programming language.
-Rather than "porting" mod_perl-1.x to Apache 2.0, mod_perl-2.0 is
+Rather than "porting" mod_perl-1.0 to Apache 2.0, mod_perl-2.0 is
being implemented as a complete re-write from scratch.
For a more detailed introduction and functionality overview, see
@@ -38,12 +38,12 @@
Apache dispatches the request to.
The interpreter pool is only enabled if Perl is built with -Dusethreads
-otherwise, mod_perl will behave just as 1.xx, using a single
+otherwise, mod_perl will behave just as 1.0, using a single
interpreter, which is only useful when Apache is configured with the
prefork mpm.
When the server is started, a Perl interpreter is constructed, compiling
-any code specified in the configuration, just as 1.xx does. This
+any code specified in the configuration, just as 1.0 does. This
interpreter is referred to as the "parent" interpreter. Then, for
the number of I<PerlInterpStart> configured, a (thread-safe) clone of the
parent interpreter is made (via perl_clone()) and added to the pool of
@@ -197,9 +197,9 @@
When a mod_perl hook is called for a given phase, the glue code has an
index into the array of handlers, so it knows to return DECLINED right
away if no handlers are configured, without entering the Perl runtime
-as 1.xx did. The handlers are also now stored in an
+as 1.0 did. The handlers are also now stored in an
apr_array_header_t, which is much lighter and faster than using a
-Perl AV, as 1.xx did. And more importantly, keeps us out of the Perl
+Perl AV, as 1.0 did. And more importantly, keeps us out of the Perl
runtime until we're sure we need to be there.
C<Perl*Handler>s are now "compiled", that is, the various forms of:
@@ -210,7 +210,7 @@
PerlResponseHandler $MyObject->handler
PerlResponseHandler 'sub { print "foo\n"; return OK }'
-are only parsed once, unlike 1.xx which parsed every time the handler
+are only parsed once, unlike 1.0 which parsed every time the handler
was used. There will also be an option to parse the handlers at
startup time. Note: this feature is currently not enabled with
threads, as each clone needs its own copy of Perl structures.
@@ -220,13 +220,13 @@
sub handler : method {};
-instead of 1.xx's
+instead of 1.0's
sub handler ($$) {}
=head1 Perl interface to the Apache API and Data Structures
-In 1.x, the Perl interface back into the Apache API and data
+In 1.0, the Perl interface back into the Apache API and data
structures was done piecemeal. As functions and structure members
were found to be useful or new features were added to the Apache API,
the xs code was written for them here and there.
@@ -423,17 +423,17 @@
=head1 Directive Handlers
-mod_perl 1.x provides a mechanism for Perl modules to implement
+mod_perl 1.0 provides a mechanism for Perl modules to implement
first-class directive handlers, but requires an xs file to be
generated and compiled. The 2.0 version will provide the same
functionality, but will not require the generated xs module.
=head1 E<lt>PerlE<gt> Configuration Sections
-The ability to write configuration in Perl will carry over from 1.x,
+The ability to write configuration in Perl will carry over from 1.0,
but will likely be implemented much different internally. The mapping
of a Perl symbol table should fit cleanly into the new
-I<ap_directive_t> API, unlike the hoop jumping required in 1.x.
+I<ap_directive_t> API, unlike the hoop jumping required in 1.0.
=head1 Protocol Module Support
@@ -452,7 +452,7 @@
=head1 Build System
-The biggest mess in 1.xx is mod_perl's Makefile.PL, the majority of
+The biggest mess in 1.0 is mod_perl's Makefile.PL, the majority of
logic has been broken down and moved to the C<Apache::Build> module.
The I<Makefile.PL> will construct an C<Apache::Build> object which
will have all the info it needs to generate scripts and I<Makefile>s
@@ -477,10 +477,10 @@
=head1 Test Framework
-Similar to 1.x, mod_perl-2.0 will provide a 'make test' target to
+Similar to 1.0, mod_perl-2.0 will provide a 'make test' target to
exercise as many areas of the API and module features as possible.
-The test framework in 1.x, like several other areas of mod_perl, was
+The test framework in 1.0, like several other areas of mod_perl, was
cobbled together over the years. The goal of 2.0 is to provide a test
framework that will be usable not only for mod_perl, but for
third-party C<Apache::*> modules and Apache itself.
@@ -495,17 +495,17 @@
C<@INC> include paths, etc.
CGI emulation will be supported in 2.0, but done so in a way that it
-is encapsulated in its own handler. Rather that 1.x which uses the
+is encapsulated in its own handler. Rather that 1.0 which uses the
same response handler, regardless if the module requires CGI emulation
or not. With an I<ithreads> enabled Perl, it will also be possible to
provide more robust namespace protection.
=head1 Apache::* Library
-The majority of the standard Apache::* modules in 1.x will be
+The majority of the standard Apache::* modules in 1.0 will be
supported in 2.0. Apache::Registry will likely be replaced with
something akin to the Apache::PerlRun/Apache::RegistryNG replacement
-prototype that exists in 1.x. The main goal being that the non-core
+prototype that exists in 1.0. The main goal being that the non-core
CGI emulation components of these modules are broken into small,
re-usable pieces to subclass Apache::Registry like behavior.
1.6 +4 -4 modperl-docs/src/docs/2.0/user/help/help.pod
Index: help.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/help/help.pod,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- help.pod 12 May 2002 05:41:22 -0000 1.5
+++ help.pod 16 Jun 2002 12:43:38 -0000 1.6
@@ -16,16 +16,16 @@
Whenever you want to report a bug or a problem remember that in order
to help you need to provide us the information about the software
blocks that you are using. This is especially important now that we
-support mod_perl versions 1.x and 2.x on the same list.
+support mod_perl versions 1.0 and 2.0 on the same list.
=head2 Wrong Apache/mod_perl combination
First of all:
- Apache 2.x doesn't work with mod_perl 1.x.
- Apache 1.x doesn't work with mod_perl 2.x.
+ Apache 2.x doesn't work with mod_perl 1.0.
+ Apache 1.x doesn't work with mod_perl 2.0.
-So if you aren't using Apache 2.x with mod_perl 2.x please do not
+So if you aren't using Apache 2.x with mod_perl 2.0 please do not
send any bug reports.
=head2 Minimum Information
1.9 +12 -12 modperl-docs/src/docs/2.0/user/overview/overview.pod
Index: overview.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/overview/overview.pod,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- overview.pod 23 May 2002 02:29:26 -0000 1.8
+++ overview.pod 16 Jun 2002 12:43:39 -0000 1.9
@@ -52,7 +52,7 @@
implementation based on lessons learned over the 4.5 years since
mod_perl was introduced.
-This document assumes basic knowlege of mod_perl-1.x features and will
+This document assumes basic knowlege of mod_perl-1.0 features and will
focus only the differences mod_perl-2.0 will bring.
Note 1: The Apache and mod_perl APIs mentioned in this document are
@@ -193,7 +193,7 @@
With 2.0 there is already a parse tree in memory, which mod_info can
then walk to output its information.
-If a mod_perl 1.xx module wants access to configuration information,
+If a mod_perl 1.0 module wants access to configuration information,
there are two approaches. A module can "subclass" directive handlers,
saving a copy of the data for itself, then returning B<DECLINE_CMD> so
the other modules are also handed the info. Or, the
@@ -247,11 +247,11 @@
each thread to have its own C<PerlInterpreter> object, or at least
that each instance is only accessed by one thread at any given time.
-mod_perl-1.xx has only a single C<PerlInterpreter>, which is
+mod_perl-1.0 has only a single C<PerlInterpreter>, which is
contructed by the parent process, then inherited across the forks to
child processes. mod_perl-2.0 has a configurable number of
C<PerlInterpreters> and two classes of interpreters, I<parent> and
-I<clone>. A I<parent> is like that in 1.xx, the main interpreter
+I<clone>. A I<parent> is like that in 1.0, the main interpreter
created at startup time which compiles any pre-loaded Perl code. A
I<clone> is created from the parent using the Perl API I<perl_clone()>
function. At request time, I<parent> interpreters are only used for
@@ -276,7 +276,7 @@
variable needs to hold a longer string than it did before, or an array
more elements than in the past. As an optimization, Perl hangs onto
these allocations, even though their values "go out of scope". With
-the 1.xx model, random children would be hit with these allocations.
+the 1.0 model, random children would be hit with these allocations.
With 2.0, mod_perl has much better control over which PerlInterpreters
are used for incoming requests. The intepreters are stored in two
linked lists, one for available interpreters, one for busy. When
@@ -391,7 +391,7 @@
pool can be used to manage any data structure, in which you wish to
have a smaller number than the number of configured threads. A good
example of such a data structure is a database connection handle.
-The C<Apache::DBI> module implements persisent connections for 1.xx,
+The C<Apache::DBI> module implements persisent connections for 1.0,
but may result in each child maintaining its own connection, when it
is most often the case that number of connections is never needed
concurrently. The TIPool API provides a mechanism to solve this
@@ -641,7 +641,7 @@
A new configuration directive to mod_perl-2.0, C<PerlOptions>,
provides fine-grained configuration for what were compile-time only
-options in mod_perl-1.xx. In addition, this directive provides
+options in mod_perl-1.0. In addition, this directive provides
control over what class of C<PerlInterpreter> is used for a
C<E<lt>VirtualHostE<gt>> or location configured with
C<E<lt>LocationE<gt>>, C<E<lt>DirectoryE<gt>>, etc.
@@ -668,7 +668,7 @@
PerlOptions None +Response
</VirtualHost>
-A common problem with mod_perl-1.xx was the shared namespace between
+A common problem with mod_perl-1.0 was the shared namespace between
all code within the process. Consider two developers using the same
server and each which to run a different version of a module with the
same name. This example will create two I<parent> Perls, one for each
@@ -713,9 +713,9 @@
host to have its own pool, that host will continue to reuse the Perl
allocations in their specific modules.
-In 1.x versions of mod_perl, configured Perl*Handlers which are not a
+In 1.0 versions of mod_perl, configured Perl*Handlers which are not a
fully qualified subroutine name are resolved at request time,
-loading the handler module from disk if needed. In 2.x, configured
+loading the handler module from disk if needed. In 2.0, configured
Perl*Handlers are resolved at startup time. By default, modules are
not auto-loaded during startup-time resolution. It is possible to
configure this feature with:
@@ -786,7 +786,7 @@
=head1 Perl interface to the APR and Apache API
-In 1.x, the Perl interface back into the Apache API and data
+In 1.0, the Perl interface back into the Apache API and data
structures was done piecemeal. As functions and structure members
were found to be useful or new features were added to the Apache API,
the xs code was written for them here and there.
@@ -797,7 +797,7 @@
public data structures are covered from the get-go. Certain functions
and structures which are considered "private" to Apache or otherwise
un-useful to Perl aren't glued. The API behaves just as it did in
-1.x, so users of the API will not notice the difference, other than the
+1.0, so users of the API will not notice the difference, other than the
addition of many new methods. And in the case of C<APR>, it is
possible to use C<APR> modules outside of Apache, for example:
1.3 +1 -1 modperl-docs/src/docs/general/multiuser.pod
Index: multiuser.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/general/multiuser.pod,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- multiuser.pod 11 May 2002 11:54:45 -0000 1.2
+++ multiuser.pod 16 Jun 2002 12:43:39 -0000 1.3
@@ -60,7 +60,7 @@
write) any other files that belong to the same user and/or group the
web server is running as. Note that L<it's impossible to run
C<suEXEC> and C<cgiwrap> extensions under
-mod_perl
1.x|guide::install/Is_it_possible_to_run_mod_perl_enabled_Apache_as_suExec_>.
+mod_perl
1.0|guide::install/Is_it_possible_to_run_mod_perl_enabled_Apache_as_suExec_>.
Another issue is the security of the database connections. If you use
C<Apache::DBI>, by hacking the C<Apache::DBI> code you can pick a
1.11 +2 -2 modperl-docs/src/download/binaries.pod
Index: binaries.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/download/binaries.pod,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- binaries.pod 16 Jun 2002 12:04:17 -0000 1.10
+++ binaries.pod 16 Jun 2002 12:43:39 -0000 1.11
@@ -14,7 +14,7 @@
=head1 How to get pre-compiled mod_perl
-=head2 Win32 mod_perl 1.x
+=head2 Win32 mod_perl 1.0
Win32 mod_perl Binaries (made by Randy Kobes) -
ftp://theoryx5.uwinnipeg.ca/pub/other/. Grab a perl-win32-bin-x.x.exe
@@ -25,7 +25,7 @@
For more information please read the L<Win32
Documentation|docs::1.0::os::win32::index>.
-=head2 Win32 mod_perl 2.x (BETA)
+=head2 Win32 mod_perl 2.0 (BETA)
An experimental mod_perl-2.0 win32 binary package is available at
ftp://theoryx5.uwinnipeg.ca/pub/other/Apache2.tar.gz for those Win32
1.3 +1 -1 modperl-docs/src/download/index_top.html
Index: index_top.html
===================================================================
RCS file: /home/cvs/modperl-docs/src/download/index_top.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- index_top.html 15 Jun 2002 14:14:58 -0000 1.2
+++ index_top.html 16 Jun 2002 12:43:39 -0000 1.3
@@ -7,7 +7,7 @@
<p>Current releases:</p>
<ul>
<li>mod_perl 1.0: <a href="http://perl.apache.org/dist/";>1.27</a>
(June 1, 2002)</li>
- <li>mod_perl 2.0 (in development): <a
href="http://perl.apache.org/dist/";>1.99_02 (beta)</a> (June 1, 2002)</li>
+ <li>mod_perl 2.0 (in development): <a
href="http://perl.apache.org/dist/";>1.99_03 (beta)</a> (June 15, 2002)</li>
</ul>
</body>
1.8 +6 -6 modperl-docs/src/download/source.pod
Index: source.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/download/source.pod,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- source.pod 10 Jun 2002 21:57:23 -0000 1.7
+++ source.pod 16 Jun 2002 12:43:39 -0000 1.8
@@ -4,16 +4,16 @@
=head1 Description
-This document explains how to get the mod_perl 1.x and 2.x source
+This document explains how to get the mod_perl 1.0 and 2.0 source
distributions.
-Please note that mod_perl 2.x is considered BETA and should not be
+Please note that mod_perl 2.0 is considered BETA and should not be
used in a production environment.
See also L<the binary distributions|download::binaries> and the
L<bundles|download::bundles>.
-=head1 mod_perl 1.x
+=head1 mod_perl 1.0
Be sure to read the I<README> and I<INSTALL> documents (in the
distribution package) and the longer L<the installation
@@ -53,13 +53,13 @@
=back
-=head1 mod_perl 2.x
+=head1 mod_perl 2.0
Be sure to read the I<README> and I<INSTALL> documents (in the
-distribution package) and the longer mod_perl 2.x L<installation
+distribution package) and the longer mod_perl 2.0 L<installation
guide|docs::2.0::user::install::install>.
-=head2 2.x Development Source Distribution
+=head2 2.0 Development Source Distribution
=over
1.16 +2 -2 modperl-docs/src/maillist/email-etiquette.pod
Index: email-etiquette.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/maillist/email-etiquette.pod,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- email-etiquette.pod 8 Jun 2002 11:29:10 -0000 1.15
+++ email-etiquette.pod 16 Jun 2002 12:43:39 -0000 1.16
@@ -29,8 +29,8 @@
=head1 How To Get Help With mod_perl Itself
Please read the sections on L<getting help with mod_perl
-1.x|docs::1.0::guide::help> or L<getting help with mod_perl
-2.x|docs::2.0::user::help::help>, depending on what version
+1.0|docs::1.0::guide::help> or L<getting help with mod_perl
+2.0|docs::2.0::user::help::help>, depending on what version
you are using.
=head2 Documentation which comes with the distribution
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
