>
> you should retry. even though it isn't the default yet,
> 'PerlModule Apache2' is a noop if modules were installed in the default
> locations. so there is no harm in always having it configured.
>
ok, I will try this, when I get a free time slot, jsut have to mange some
other things before...
>
> there is no need for extra code logic to run with both 1.x and 2.x, there
> are only configuration changes. PerlModule Apache::compat will map the
> old 1.x api to the new 2.x api. granted, there are still gaps to fill in,
> and we do that as they pop up. and there are some cases where the code
> must change, for example $r->connection->user must be $r->user to work
> with 2.x. 1.x added $r->user back in 1.24_01. there is also the lack of
> some features at the moment in 2.x such as directive handlers. but for
> the common cases, Apache::compat takes care of most.
>
I am currently porting Embperl to mod_perl 2 and Embperl doesn't use much of
the Perl stuff, so I tried to load only the necessary things to not fill up
the memory with unused Perl code. So Embperl is a little different then
other modules, which are pure Perl.
Now I have some more experiences, as at the time when I start porting and I
looked at Apache::compat again and I see you are right (of course you are
right, since you know what you have done :-). Loading Apache::compat should
avoid all of the mod_perl 2 conditions in Embperl itself. The only thing
that is missing at the moment and I think you should add it, is a
require Apache::SubRequest ;
otherwise $r -> lookup_uri etc doesn't work.
The otherthing is the test suite, which need to know which version we are
using and startup.pl need to decide to load Apache::Registry or
ModPerl::Registry. I currently check $ENV{MOD_PERL}, is there a better way
to decide, if we are running under mod_perl, something like
$ModPerl::MajorVersion == 2 would be cool?
> the modperl core modules themselves, such as Apache::Connection, has no
> chance whatsoever to run with both 1.3 and 2.0.
of course
> which is exactly why we
> provide the MP_INST_APACHE2 option, so both versions can live in the same
> install tree.
The question is, why not always install under Apache2? As you said
Apache::compat maps it to the Apache namespace, so 1.3 modules will continue
to run? What is the benefit of installing under Apache instead of Apache2?
Maybe I am wrong, but at the moment I think it would be much easier for the
normal user to always install under Apache2 and tell them to use
Apache::compat when they want to use old modules.
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
