Re: mod-perl_2.0

[Per Einar Ellefsen]

At 00:25 29.05.2002, Kent, Mr. John wrote:
>Now my question.  In the older version,(126) mod-perl created a larger
>(heavy)
>webserver.  I could then add a startup.pl file to its http.conf file
>which used Apache::Registry to load perl and my modules.
>
>I don't see how this works in the new version of mod-perl, because
>I don't see a "larger" version of the httpd server anywhere.
>
>When I did the install it just seemed to load into the Perl 5.6.1 libraries.

We'll need some more information about your build process... Normally, you 
specify the Apache Prefix (or the location of apxs) when running perl 
Makefile.PL. Then, you run make for mod_perl, ./configure and make for 
Apache 2.0, make test for mod_perl and I guess finally make install on both 
parts.

You should see the mod_perl 2 installation documents: 
http://perl.apache.org/release/docs/2.0/user/index.html

>Did notice in the overview
>"The details of these optimizations from the most part are hidden from
> mod_perl users, the exception being that some will only be turned on
> with configuration directives. A few of which include:
> *   Inlined "Apache::*.xs" calls
>"
>But not sure how to use it.

This isn't really related to your question.. Look through the 
documentation, but for the most part these optimizations happen without you 
noticing.


-- 
Per Einar Ellefsen
[EMAIL PROTECTED]

Re: mod-perl_2.0

[Andrew McNaughton]

On Tue, 28 May 2002, Kent, Mr. John wrote:

> So how does this work now?  If it doesn't or it would take too much
> time to explain it, I certainly can understand and will simply load and
> continue to use Apache 1.3.24 and mod-perl 1.26

Things may have changed, in which case someone will gainsay me, but my
understanding is that modperl with apache 2 is not reccomended for
production use.  My guess is that while there will be early adopters,
apache 2 will take at least a year to become the standard.  A lot has
changed, and for most users there's no compelling reason to update.

Andrew