stas 2002/06/10 03:53:58
Modified: src/docs/2.0/os/win32 config.pod install.pod
Log:
fix links and markup
adjust to be consistent with the rest of docs to use 1.0, 2.0 notation for
mod_perl and 1.3, 2.0 for Apache
some wrapping
Revision Changes Path
1.4 +31 -31 modperl-docs/src/docs/2.0/os/win32/config.pod
Index: config.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/os/win32/config.pod,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- config.pod 2 Jun 2002 03:40:44 -0000 1.3
+++ config.pod 10 Jun 2002 10:53:58 -0000 1.4
@@ -4,7 +4,7 @@
=head1 Description
-This document discusses how to configure mod_perl-2.
+This document discusses how to configure mod_perl 2.0.
=head1 Configuration
@@ -13,9 +13,9 @@
LoadModule perl_module modules/mod_perl.so
Be sure that the path to your Perl binary (eg, F<C:/Perl/bin>) is in
-your C<PATH> environment variable. You may also want to use
-a start-up script to load commonly used modules; this can be
-done with a directive as, eg,
+your C<PATH> environment variable. You may also want to use a start-up
+script to load commonly used modules; this can be done with a
+directive as, eg,
PerlRequire "C:/Apache2/conf/extra.pl"
@@ -38,14 +38,14 @@
use CGI ();
1;
-The C<Apache2> module is used to add to C<@INC> the
-relevant directories underneath, eg, F</Perl/site/lib/Apache2/>
-used when building mod_perl-2 with an C<MP_INST_APACHE2=1>
-option to C<perl Makefile.PL> (the C<PPM> packages discussed
-above were built this way). C<Apache::compat> is used to
-provide backwards compatibility with mod_perl-1.
-C<ModPerl::Registry>, named so as not to conflict with
-C<Apache::Registry> of mod_perl-1, is used for registry scripts.
+The C<Apache2> module is used to add to C<@INC> the relevant
+directories underneath, eg, F</Perl/site/lib/Apache2/> used when
+building mod_perl 2.0 with an C<MP_INST_APACHE2=1> option to C<perl
+Makefile.PL> (the C<PPM> packages discussed above were built this
+way). C<Apache::compat> is used to provide backwards compatibility
+with mod_perl 1.0. C<ModPerl::Registry>, named so as not to conflict
+with C<Apache::Registry> of mod_perl 1.0, is used for registry
+scripts.
=head1 Registry scripts
@@ -67,8 +67,8 @@
#sleep(10);
print "</UL></BODY></HTML>";
-Note that Apache takes care of using the proper line endings
-when sending the I<Content-type> header. Next, insert in
+Note that Apache takes care of using the proper line endings when
+sending the I<Content-type> header. Next, insert in
F<C:/Apache2/conf/httpd.conf> the following directives:
Alias /perl/ "/Apache2/perl/"
@@ -84,20 +84,20 @@
http://localhost/perl/name_of_script
The C<PerlOptions +ParseHeaders> directive is needed when the script
-sends the header (in mod_perl-1, this was given as C<PerlSendHeader
+sends the header (in mod_perl 1.0, this was given as C<PerlSendHeader
ON)>.
-As an illustration of how mod_perl-2 addresses the issues raised in
+As an illustration of how mod_perl 2.0 addresses the issues raised in
the discussion of issues in L<multithread
win32|docs::1.0::os::win32::multithread> concerning the threading
-limitations of mod_perl-1 on Win32, consider the C<printenv> script
+limitations of mod_perl 1.0 on Win32, consider the C<printenv> script
above with the C<sleep(10)> line uncommented. Using the Apache
-benchmarking tool C<ab> of the Apache-2 Win32 distribution:
+benchmarking tool C<ab> of the Apache 2.0 Win32 distribution:
C:\Apache2\bin> ab -n 5 -c 5 http://localhost/perl/printenv
to make 5 concurrent requests, we find the following results. For
-mod_perl-1/Apache-1:
+mod_perl 1.0/Apache 1.3:
Server Software: Apache/1.3.23
Concurrency Level: 5
@@ -109,7 +109,7 @@
Time per request: 10.010 [ms] (mean, across all concurrent requests)
Transfer rate: 0.14 [Kbytes/sec] received
-while for mod_perl-2/Apache-2:
+while for mod_perl 2.0/Apache 2.0:
Server Software: Apache/2.0.36
Concurrency Level: 5
@@ -120,10 +120,11 @@
Time per request: 0.216 [ms] (mean, across all concurrent requests)
Transfer rate: 7.40 [Kbytes/sec] received
-The dramatic difference is due to the fact that in Apache-1/mod_perl-1
-a given request has to finish (taking essentially 10 seconds, due
-to the C<sleep(10)> call) before the next request is processed, whereas
-on Apache-2/mod_perl-2 the requests are processed as they arrive.
+The dramatic difference is due to the fact that in Apache 1.3/mod_perl
+1.0 a given request has to finish (taking essentially 10 seconds, due
+to the C<sleep(10)> call) before the next request is processed,
+whereas on Apache 2.0/mod_perl 2.0 the requests are processed as they
+arrive.
=head1 Hello World
@@ -173,13 +174,12 @@
=head1 See Also
-The directions for
-<installing mod_perl-2 on Win32|docs::1.0::os::win32::install>,
-the L<mod_perl documentation|docs::index>,
-http://perl.apache.org/, http://take23.org/,
-http://httpd.apache.org/, and http://www.activestate.com/.
-Help on setting up and configuring mod_perl-2 can be
-found by subscribing to the mod_perl mailing list,
+The directions for L<installing mod_perl 2.0 on
+Win32|docs::2.0::os::win32::install>, the L<mod_perl
+documentation|docs::index>, http://perl.apache.org/,
+http://take23.org/, http://httpd.apache.org/, and
+http://www.activestate.com/. Help on setting up and configuring
+mod_perl 2.0 can be found by subscribing to the mod_perl mailing list,
details of which are at http://perl.apache.org/.
=head1 Maintainers
1.3 +88 -97 modperl-docs/src/docs/2.0/os/win32/install.pod
Index: install.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/os/win32/install.pod,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- install.pod 31 May 2002 02:47:01 -0000 1.2
+++ install.pod 10 Jun 2002 10:53:58 -0000 1.3
@@ -4,101 +4,94 @@
=head1 Description
-As described in the discussion of issues in
-L<multithreaded win32|docs::1.0::os::win32::multithread>,
-a mod_perl-1 enabled
-server based on Apache-1 on Win32 is limited to a single
-thread serving a request at a time. This effectively
-prevents concurrent processing, which can have serious
-implications for busy sites. This problem is addressed
-in the multi-thread/multi-process approach of mod_perl-2/Apache-2.
-This document discusses how to obtain mod_perl-2.
+This document deals with installation specifics on Win32 platforms.
+
+As described in the discussion of issues in L<multithreaded
+win32|docs::1.0::os::win32::multithread>, a mod_perl 1.0 enabled server
+based on Apache 1.3 on Win32 is limited to a single thread serving a
+request at a time. This effectively prevents concurrent processing,
+which can have serious implications for busy sites. This problem is
+addressed in the multi-thread/multi-process approach of mod_perl
+2.0/Apache 2.0. This document discusses how to obtain mod_perl 2.0.
=head1 Installing
-Apache-2 and mod_perl-2 can be obtained in two ways - either
-as binaries, or through building from the sources.
-As with most packages of a more complex nature, it is best,
-when possible, to build things from the sources. However,
-this requires some experience with using Visual C++.
+Apache 2.0 and mod_perl 2.0 can be obtained in two ways - either as
+binaries, or through building from the sources. As with most packages
+of a more complex nature, it is best, when possible, to build things
+from the sources. However, this requires some experience with using
+Visual C++.
=head2 Building from sources
-If you are building mod_perl-2 from sources, it is probably
-also best to do the same for Apache-2. The Apache-2 sources
-can be obtained from http://httpd.apache.org/, which when
-unpacked will contain at the top-level a Visual Studio
-project file. Choose the C<InstallBin - Win32 Release> target
-to build and install Apache-2, which by default will
-be placed in F</Apache2>.
-
-Having built and installed Apache-2, next obtain the
-mod_perl-2 sources from http://www.cpan.org/authors/id/D/DO/DOUGM/.
-After unpacking, run the command
+If you are building mod_perl 2.0 from sources, it is probably also
+best to do the same for Apache 2.0. The Apache 2.0 sources can be
+obtained from http://httpd.apache.org/, which when unpacked will
+contain at the top-level a Visual Studio project file. Choose the
+C<InstallBin - Win32 Release> target to build and install Apache 2.0,
+which by default will be placed in F</Apache2>.
+
+Having built and installed Apache 2.0, next obtain the mod_perl 2.0
+sources from http://www.cpan.org/authors/id/D/DO/DOUGM/. After
+unpacking, run the command
C:\modperl_src> perl Makefile.PL MP_AP_PREFIX=\Path\to\Apache2
-where F<\Path\to\Apache2> is the path to the Apache-2
-package you earlier built. Then
+where F<\Path\to\Apache2> is the path to the Apache 2.0 package you
+earlier built. Then
C:\modperl_src> nmake
C:\modperl_src> nmake test
-will build and test mod_perl-2. mod_perl-2 on Win32 is
-considered at an alpha stage of development, so not
-all the tests may pass.
+will build and test mod_perl 2.0. mod_perl 2.0 on Win32 is considered
+at an alpha stage of development, so not all the tests may pass.
The final command,
C:\modperl_src> nmake install
-will install the necessary mod_perl-2 files into your
-Perl directory tree (you will also need to copy
-F<src/modules/perl/mod_perl.so> into your F</Path/to/Apache2/modules/>
-directory). If you are installing mod_perl-2 on a system that
-also contains mod_perl-1, then some mod_perl-1 files will be
-overwritten by this procedure. This can be avoided by preparing
-the build as
+will install the necessary mod_perl 2.0 files into your Perl directory
+tree (you will also need to copy F<src/modules/perl/mod_perl.so> into
+your F</Path/to/Apache2/modules/> directory). If you are installing
+mod_perl 2.0 on a system that also contains mod_perl 1.0, then some
+mod_perl 1.0 files will be overwritten by this procedure. This can be
+avoided by preparing the build as
C:\modperl_src> perl Makefile.PL MP_AP_PREFIX=\Path\to\Apache2
MP_INST_APACHE2=1
-which will subsequently lead to the mod_perl-2 files
-being installed under an F<Apache2> subdirectory in your Perl tree.
-You will then have to employ either a C<use Apache2;> line in your
-scripts/packages or else a C<PerlModule Apache2> directive in
-Apache's F<httpd.conf>.
-
-If this build fails, you may want to try the latest cvs
-sources - see http://perl.apache.org/mod_perl_cvs.html for
-details. If you do try this, it is generally
-a good idea to also use the cvs Apache-2 sources -
-see http://httpd.apache.org/dev/ for information. Be aware,
-though, that as well as providing
-bug fixes, there may be new features being added and tested
-in the cvs versions, so at any given time there are no
-guarantees that these packages will build and test successfully.
+which will subsequently lead to the mod_perl 2.0 files being installed
+under an F<Apache2> subdirectory in your Perl tree. You will then
+have to employ either a C<use Apache2;> line in your scripts/packages
+or else a C<PerlModule Apache2> directive in Apache's F<httpd.conf>.
+
+If this build fails, you may want to try the latest cvs sources - see
+http://perl.apache.org/mod_perl_cvs.html for details. If you do try
+this, it is generally a good idea to also use the cvs Apache 2.0 sources
+- see http://httpd.apache.org/dev/ for information. Be aware, though,
+that as well as providing bug fixes, there may be new features being
+added and tested in the cvs versions, so at any given time there are
+no guarantees that these packages will build and test successfully.
=head2 Binary packages
-There are two ways of obtaining a binary mod_perl-2 package.
+There are two ways of obtaining a binary mod_perl 2.0 package.
=over 3
=item PPM
-The first, for ActivePerl users, is through C<PPM> - this
-assumes you already have ActivePerl (build 6xx) from
-http://www.activestate.com/ and a Win32 Apache-2 binary
-from http://httpd.apache.org/. In installing
-this, you may find it convenient when transcribing any Unix-oriented
-documentation to choose installation directories that do not have
-spaces in their names (eg, F<C:/Apache2>).
-
-After installing Perl and Apache-2, you can then install mod_perl via
-the C<PPM> utility. ActiveState does not maintain mod_perl in their ppm
-repository, so you must get it from a different location other than
-ActiveState's site. One way is simply as (broken over two lines for
-readability)
+The first, for ActivePerl users, is through C<PPM> - this assumes you
+already have ActivePerl (build 6xx) from http://www.activestate.com/
+and a Win32 Apache 2.0 binary from http://httpd.apache.org/. In
+installing this, you may find it convenient when transcribing any
+Unix-oriented documentation to choose installation directories that do
+not have spaces in their names (eg, F<C:/Apache2>).
+
+After installing Perl and Apache 2.0, you can then install mod_perl
+via the C<PPM> utility. ActiveState does not maintain mod_perl in
+their ppm repository, so you must get it from a different location
+other than ActiveState's site. One way is simply as (broken over two
+lines for readability)
C:\> ppm install
http://theoryx5.uwinnipeg.ca/ppmpackages/mod_perl-2.ppd
@@ -115,23 +108,23 @@
PPM> rep add theoryx5
http://theoryx5.uwinnipeg.ca/cgi-bin/ppmserver?urn:/PPMServer
-mod_perl-2 can then be installed as
+mod_perl 2.0 can then be installed as
PPM> install mod_perl-2
This will install the necessary modules under an F<Apache2>
-subdirectory in your Perl tree, so as not to disturb an
-existing F<Apache> directory from mod_perl-1. See the section
-below on configuring mod_perl to add this directory to the
-C<@INC> path for searching for modules.
+subdirectory in your Perl tree, so as not to disturb an existing
+F<Apache> directory from mod_perl 1.0. See the section below on
+configuring mod_perl to add this directory to the C<@INC> path for
+searching for modules.
The mod_perl PPM package also includes the necessary Apache DLL
C<mod_perl.so>; a post-installation script should be run which will
offer to copy this file to your Apache2 modules directory (eg,
-F<C:/Apache2/modules/>). If this is not done, you can get
-the file F<mod_perl-2.tar.gz> from
-http://theoryx5.uwinnipeg.ca/ppmpackages/x86/ which, when
-unpacked, contains F<mod_perl.so> in the top-level directory.
+F<C:/Apache2/modules/>). If this is not done, you can get the file
+F<mod_perl-2.tar.gz> from
+http://theoryx5.uwinnipeg.ca/ppmpackages/x86/ which, when unpacked,
+contains F<mod_perl.so> in the top-level directory.
Note that the mod_perl package available from this site will always
use the latest mod_perl sources compiled against the latest official
@@ -142,34 +135,32 @@
=item Apache/mod_perl binary
-At ftp://theoryx5.uwinnipeg.ca/pub/other/ one can find an
-archive F<Apache2.tar.gz> containing a binary version
-of Apache-2/mod_perl-2 - see the F<Apache2.readme> file
-for further information. This archive unpacks into
-an F<Apache2> directory, underneath which is a F<blib>
-subdirectory containing the necessary mod_perl files (enabled
-with a C<PerlSwitches> directive in F<httpd.conf>).
-Some editing of F<httpd.conf> will be necessary to reflect
-the location of the installed directory.
-
-This package, which is updated periodically, is compiled against
-recent cvs sources of Apache-2 and mod_perl-2. As such, it may
-contain features, and bugs, not present in the current official
+At ftp://theoryx5.uwinnipeg.ca/pub/other/ one can find an archive
+F<Apache2.tar.gz> containing a binary version of Apache 2.0/mod_perl
+2.0 - see the F<Apache2.readme> file for further information. This
+archive unpacks into an F<Apache2> directory, underneath which is a
+F<blib> subdirectory containing the necessary mod_perl files (enabled
+with a C<PerlSwitches> directive in F<httpd.conf>). Some editing of
+F<httpd.conf> will be necessary to reflect the location of the
+installed directory.
+
+This package, which is updated periodically, is compiled against
+recent cvs sources of Apache 2.0 and mod_perl 2.0. As such, it may
+contain features, and bugs, not present in the current official
releases. Also for this reason, these may not be binary compatible
-with other versions of Apache-2/mod_perl-2.
+with other versions of Apache 2.0/mod_perl 2.0.
=back
=head1 See Also
-The directions for
-<configuring mod_perl-2 on Win32|docs::1.0::os::win32::config>,
-the L<mod_perl documentation|docs::index>,
-http://take23.org/,
-http://httpd.apache.org/, and http://www.activestate.com/.
-Help on setting up and configuring mod_perl-2 can be
-found by subscribing to the mod_perl mailing list,
-details of which are at http://perl.apache.org/.
+The directions for L<configuring mod_perl 2.0 on
+Win32|docs::2.0::os::win32::config>, the L<mod_perl
+documentation|docs::index>, http://take23.org/,
+http://httpd.apache.org/, and http://www.activestate.com/. Help on
+setting up and configuring mod_perl 2.0 can be found by subscribing to
+the mod_perl mailing list, details of which are at
+http://perl.apache.org/.
=head1 Maintainers
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
