Thanks William. Actually migrating the legacy code to Apache2 and
mod_perl2 is what my client wants to avoid due to the cost of conversion.
(The cost of conversion is way beyond any recoding and testing -- it's
dictated by policy for a very active app with a large customer base that
would require parallel old and new systems for a substantial period. This
is the greater cost.) The choice seems to boil down to continuing to run
on 1, or using the compat module, but the potential performance issues and
non-zero conversion cost even with compat means we'll probably continue with
1, unless I can reactivate those dormant brain cells from the earlier
experience. :-(
Jim
-----Original Message-----
From: William Whalen
Sent: Saturday, June 18, 2011 1:23 PM
To: James Eshelman
Cc: [email protected]
Subject: Re: [Boston.pm] Apache/mod_perl 2 => 1?
At 10:14 AM 6/18/2011 -0400, James Eshelman wrote:
A while back I worked with a big perl app running under mod_perl and
apache2, but actually running in version 1 mode. The problem is that the
details of how this was accomplished are a bit sketchy in my mind.
Apache2::compat was definitely part of it and is well documented on the mod
perl site, but I have this nagging feeling that there was more to it than
that and what I find on the mod_perl site. Anyone have any pointers on
doing this?
It sounds like you are migrating an existing mod_perl 1 application
to mod_perl 2.
For mostly good reasons, the interface and conventions changed
greatly from version one to two of mod_perl, and the migration takes a bit
of revising. Apache2::compat may make the earlier application
function, at a potentially high run-time cost, and it is meant to
be a temporary transition piece.
You have found the on-line docs, which are not always
easy to read but will repay attention.
The mod_perl users list is a very good forum:
http://perl.apache.org/maillist/modperl.html
This book is especially helpful (although the online
material overlaps greatly and sometimes is more current):
http://modperl2book.org/
One can do a great deal with mod_perl, but it is
rather its own entity.
William
([email protected])
_______________________________________________
Boston-pm mailing list
[email protected]
http://mail.pm.org/mailman/listinfo/boston-pm
