stas 02/01/02 01:39:31
Modified: . perl_myth.pod
faq mod_perl_api.pod mod_perl_faq.pod
Log:
- escape [><] chars
Revision Changes Path
1.6 +18 -16 modperl-site/perl_myth.pod
Index: perl_myth.pod
===================================================================
RCS file: /home/cvs/modperl-site/perl_myth.pod,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- perl_myth.pod 22 Aug 2001 02:26:19 -0000 1.5
+++ perl_myth.pod 2 Jan 2002 09:39:31 -0000 1.6
@@ -34,10 +34,12 @@
is then kept into memory and used each time the program is run. In
this way there is no extra overhead when hitting a mod_perl page.
-=over 4
+=back
=head3 Interpreted vs. Compiled (More Gory Details)
+=over 4
+
=item R:
Compiled code always has the potential to be faster than interpreted
@@ -63,8 +65,6 @@
=back
-=back
-
=head2 Perl is overly memory intensive making it unscalable
=over 4
@@ -90,10 +90,12 @@
some platforms (I believe ELF is one such format) are able to share
entire executable TEXT segments between unrelated processes.
-=over 4
+=back
=head3 More Tuning Advice:
+=over 4
+
=item *
B<Vivek Khera's mod_perl performance tuning guide>( http://perl.apache.org/tuning/ )
@@ -104,8 +106,6 @@
=back
-=back
-
=head2 Not enough support, or tools to develop with Perl. (Myth)
=over 4
@@ -240,43 +240,45 @@
=item *
-Stas Bekman <[EMAIL PROTECTED]>
+Stas Bekman E<lt>[EMAIL PROTECTED]<gt>
=item *
-Thornton Prime <[EMAIL PROTECTED]>
+Thornton Prime E<lt>[EMAIL PROTECTED]<gt>
=item *
-Chip Turner <[EMAIL PROTECTED]>
+Chip Turner E<lt>[EMAIL PROTECTED]<gt>
=item *
-Clinton <[EMAIL PROTECTED]>
+Clinton E<lt>[EMAIL PROTECTED]<gt>
=item *
-Joshua Chamas <[EMAIL PROTECTED]>
+Joshua Chamas E<lt>[EMAIL PROTECTED]<gt>
=item *
-John Edstrom <[EMAIL PROTECTED]>
+John Edstrom E<lt>[EMAIL PROTECTED]<gt>
=item *
-Rasmus Lerdorf <[EMAIL PROTECTED]>
+Rasmus Lerdorf E<lt>[EMAIL PROTECTED]<gt>
=item *
-Nedim Cholich <[EMAIL PROTECTED]>
+Nedim Cholich E<lt>[EMAIL PROTECTED]<gt>
=item *
-Mike Perry < http://www.icorp.net/icorp/feedback.htm >
+Mike Perry E<lt> http://www.icorp.net/icorp/feedback.htm E<gt>
=item *
-Finally, I'd like to thank Robert Santos <[EMAIL PROTECTED]>, CyberNation's lead
Business Development guy for inspiring this document.
+Finally, I'd like to thank Robert Santos E<lt>[EMAIL PROTECTED]<gt>,
+CyberNation's lead Business Development guy for inspiring this
+document.
=back
1.6 +7 -9 modperl-site/faq/mod_perl_api.pod
Index: mod_perl_api.pod
===================================================================
RCS file: /home/cvs/modperl-site/faq/mod_perl_api.pod,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- mod_perl_api.pod 18 Jul 2001 02:29:28 -0000 1.5
+++ mod_perl_api.pod 2 Jan 2002 09:39:31 -0000 1.6
@@ -1,10 +1,6 @@
=head1 NAME
-<<<<<<< mod_perl_api.pod
-Mod_perl_api - accessing the Apache API via mod_perl ($Date: 2001/07/18 02:29:28 $)
-=======
-Mod_perl_api - accessing the Apache API via mod_perl ($Date: 2001/07/18 02:29:28 $)
->>>>>>> 1.2
+Mod_perl_api - accessing the Apache API via mod_perl
=head1 DESCRIPTION
@@ -33,7 +29,7 @@
If this directive is put in access.conf outside of any restrictive
context, your handler will be called during the given phase of each
request processed by the server. You can make it more selective by
-restricting it to a directory (-hierarchy) in a <Directory ...>
+restricting it to a directory (-hierarchy) in a E<lt>Directory ...E<gt>
section of access.conf or by putting it in a .htaccess file.
Here is an example of the directives needed to call a handler during
@@ -109,9 +105,9 @@
Ralf Engelschall writes:
When you compiled one httpd with and the other without mod_perl, then
-you can simply use <IfModule mod_perl.c>...</IfModule> to surround the
-stuff for the httpd compiled with mod_perl. The other then ignores
-these lines. Example:
+you can simply use E<lt>IfModule mod_perl.cE<gt>...E<lt>/IfModuleE<gt>
+to surround the stuff for the httpd compiled with mod_perl. The other
+then ignores these lines. Example:
<IfModule mod_perl.c>
...stuff for httpd w/ mod_perl...
@@ -119,3 +115,5 @@
<IfModule !mod_perl.c>
...stuff for httpd w/o mod_perl...
</IfModule>
+
+=cut
1.11 +2 -2 modperl-site/faq/mod_perl_faq.pod
Index: mod_perl_faq.pod
===================================================================
RCS file: /home/cvs/modperl-site/faq/mod_perl_faq.pod,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- mod_perl_faq.pod 16 Oct 2001 16:08:34 -0000 1.10
+++ mod_perl_faq.pod 2 Jan 2002 09:39:31 -0000 1.11
@@ -1,6 +1,6 @@
=head1 NAME
-Mod_perl_faq - frequently asked questions about mod_perl ($Date: 2001/10/16
16:08:34 $)
+Mod_perl_faq - frequently asked questions about mod_perl ($Date: 2002/01/02
09:39:31 $)
=head1 DESCRIPTION
@@ -26,7 +26,7 @@
The primary advantages of mod_perl are power and speed. You have full
access to the inner-workings of the web server and can intervene at any
stage of request-processing. This allows for customized processing of (to
-name just a few of the phases) URI->filename translation, authentication,
+name just a few of the phases) URI-E<gt>filename translation, authentication,
response generation and logging. There is very little run-time overhead.
In particular, it is not necessary to start a separate process, as is
often done with web-server extensions. The most wide-spread such
