Re: cgi to mod_perl?

2010-02-08 Thread André Warnier

tech list wrote:

Hi again,

We have the projects which were written by perl CGI.
All programs and modules are developed with good style, use strict
and use warnings are enabled.
Can we simply move all the scripts to run under modperl's Registry?
Will they go without problems? How much improvement for the performance?


About your last question : a lot.
About the other question :
It depends. Generally, yes. But you should really read the documentation 
here : http://perl.apache.org/docs/2.0/user/index.html
The time you will spend initially reading this documentation, will be 
saved 100 times afterward.

Also, start with Apache 2.2 and mod_perl 2.x.
Do not start with Apache 1.3/mod_perl 1.x.
The Apache 1.3 end of life announcement has just gone out, and there 
is no reason to lose time with it, nor spend your time later doing a 
mod_perl-1 to mod_perl-2 conversion.





Re: cgi to mod_perl?

2010-02-08 Thread tech list
On Mon, Feb 8, 2010 at 4:29 PM, André Warnier a...@ice-sa.com wrote:

 About your last question : a lot.
 About the other question :
 It depends. Generally, yes. But you should really read the documentation
 here : http://perl.apache.org/docs/2.0/user/index.html
 The time you will spend initially reading this documentation, will be saved
 100 times afterward.
 Also, start with Apache 2.2 and mod_perl 2.x.


Thanks for your kind suggestion.


Re: PerlOptions +Parent

2010-02-08 Thread Philippe M. Chiasson
On 10-02-01 06:32 , Torsten Förtsch wrote:
 On Monday 01 February 2010 11:48:19 Carl Johnstone wrote:
 So rather than +Parent which just gives a VirtualHost a separate instance
  -  what would be nice would be some way of specifying which perl instance
  to use in this VirtualHost. Something like:

 VirtualHost *
 ServerName www.example1.com
 PerlInstance myappv4
 /VirtualHost

 VirtualHost *
 ServerName www.example2.com
 PerlInstance myappv4
 /VirtualHost

 Feasible by patching modperl's interpreter pool handling.

Yes. and mod_python, IIRC, has such a mechanism. Might be worth
implementing, if there is a use for it.

 But how about using several apache instances and a mod_proxy-based proxy in 
 front to pass the requests to the appropriate instance? This can be 
 implemented without patching modperl.

That solution would also be my choice.

-- 
Philippe M. Chiasson GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/   m/gozer\@(apache|cpan|ectoplasm)\.org/



signature.asc
Description: OpenPGP digital signature


[RELEASE CANDIDATE] Apache-Test-1.31 RC1

2010-02-08 Thread Fred Moyer
Greetings,

Please, download, test, and report back on success or failure for this
Apache::Test release candidate.

Development from 1.30 has been ongoing for about two years, so this is
as good a time as ever to make a release.

http://people.apache.org/~phred/Apache-Test-1.31-rc1.tar.gz


svn commit: r907947 - /perl/Apache-DBI/trunk/RELEASE

2010-02-08 Thread phred
Author: phred
Date: Tue Feb  9 07:16:34 2010
New Revision: 907947

URL: http://svn.apache.org/viewvc?rev=907947view=rev
Log:
Update the release file for 1.09

Modified:
perl/Apache-DBI/trunk/RELEASE

Modified: perl/Apache-DBI/trunk/RELEASE
URL: 
http://svn.apache.org/viewvc/perl/Apache-DBI/trunk/RELEASE?rev=907947r1=907946r2=907947view=diff
==
--- perl/Apache-DBI/trunk/RELEASE (original)
+++ perl/Apache-DBI/trunk/RELEASE Tue Feb  9 07:16:34 2010
@@ -1,9 +1,9 @@
 1) find . -type f | egrep -v '.svn|RELEASE' | \
-   xargs perl -pi -e 's,1.07-dev,1.08,g'
+   xargs perl -pi -e 's,1.09-dev,1.09,g'
 
-   Update Changes - add the date for 1.08 entry
+   Update Changes - add the date for 1.09 entry
 
-   svn ci -m prep 1.08 release
+   svn ci -m prep 1.09 release
 
 2) make distclean
 
@@ -13,16 +13,16 @@
 
 5) make dist clean
 
-6) svn copy -m tag 1.08 \
+6) svn copy -m tag 1.09 \
https://svn.perl.org/modules/Apache-DBI/trunk \
-   https://svn.perl.org/modules/Apache-DBI/tags/rel_1_08
+   https://svn.perl.org/modules/Apache-DBI/tags/rel_1.09
 
 7) find . -type f | egrep -v '.svn|Changes|RELEASE' | \
-   xargs perl -pi -e 's,1.08,1.08-dev,g'
+   xargs perl -pi -e 's,1.09,1.10-dev,g'
 
-8) Add an entry to Changes for 1.08-dev
+8) Add an entry to Changes for 1.10-dev
 
-9) svn ci -m roll on to 1.08-dev
+9) svn ci -m roll on to 1.10-dev
 
 10) forward the PAUSE email with MD5 sum and Changes to 
 modp...@perl.apache.org.