William McKee wrote:
--- testing.pod.orig 2004-01-14 22:15:37.000000000 -0500
+++ testing.pod 2004-01-14 21:16:30.000000000 -0500
@@ -361,7 +358,7 @@
in order to try to detect as many problems as possible during the
testing process, it's may be useful to run tests in different orders.
-This if of course mosly useful in conjunction with I<-times=N> option.
+This is of course mostly useful in conjunction with I<-times=N> option.
-we can see exactly what's the problem, by visual expecting of the
+we can see exactly what's the problem, by visual examinination of the
expected and received values.
Committed, thanks
Assuming that we have tests a, b and c:
@@ -900,10 +897,13 @@
#-------------------------
# this file will be Include-d by @ServerRoot@/httpd.conf
- # where Apache::Amazing can be found
- PerlSwitches [EMAIL PROTECTED]@/../lib
- # preload the module
- PerlModule Apache::Amazing
+ <IfDefine MODPERL2>
+ # This section is not necessary but can provide better performance
+ # where Apache::Amazing can be found
+ PerlSwitches [EMAIL PROTECTED]@/../lib
+ # preload the module
+ PerlModule Apache::Amazing
+ </IfDefine>
<Location /test/amazing>
SetHandler modperl
PerlResponseHandler Apache::Amazing
I didn't commit this part. I'm not sure we want to duplicate the porting guide in this document. Instead of duplicating things, I've added a section telling that this document uses mp2 in examples and gave a pointer to the chapter explaining how to write config files and code that will co-exist under both mod_perl generations. (it'll be online within 6 hours, or update your cvs)
http://cvs.apache.org/viewcvs.cgi/modperl-docs/src/docs/general/testing/testing.pod
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
