On Sun, 2 Jun 2002, Gerald Richter wrote: > I don't use this option, because it's not the default and I want to test the > default case (at least for the moment) and when I last tried it (ok, this > was long ago) it didn't work, because it is not the default and it seems > that at this time nobody had used it. Maybe I should retry it....
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. > >From my expericence with the step from Embperl 1.x to Embperl 2.x I would > say: yes make it the default. Since mod_perl 2 isn't (and can't) be 100% > compatible with 1.x, it is not a drop in replacement and if you have a set > of applications that are running fine with 1.x, there is no need to rewrite > (normaly you won't have the time, to adapt them to 2.x), but for new > application you may want to use 2.x. The backdraw is that modules that tries > to run with both versions, need some extra logic, but they will need it > anyway, since this option exists and poeple will use it. > > I think we need a smooth upgrade path, nobody will switch in one day. 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. the modperl core modules themselves, such as Apache::Connection, has no chance whatsoever to run with both 1.3 and 2.0. which is exactly why we provide the MP_INST_APACHE2 option, so both versions can live in the same install tree. however, a pure-perl module that uses modperl core modules should not have to be changed to run with both 1.3 and 2.0 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
