Perrin Harkins wrote:
Geoffrey Young wrote:
so I see no harm in letting the masses get their feet wet with 2.0
now. we have lots of people installing it on lots of different
platforms, so getting past the initial installation hurdle shouldn't
be any more difficult than with 1.0. after that, t
Perrin Harkins wrote:
I recently gave some advice on perlmonks.org to a person who was
concerned about what his migration path would be if he develops for
mod_perl 1 right now. I told him he will be safe if he uses
Apache::Registry, since he should be able to run his A::R scripts under
ModPerl::Re
That's actually the reason I didn't recommend starting with mp2 to this
guy: the documentation. It's easy for me to look at things and say "oh,
this corresponds to the 1.0 docs here", but to a newbie that will sound
like insanity. There's a lot more documented than there used to be, and
I am
Geoffrey Young wrote:
so I see no harm in letting the masses get their feet wet with 2.0 now.
we have lots of people installing it on lots of different platforms, so
getting past the initial installation hurdle shouldn't be any more
difficult than with 1.0. after that, the main API hasn't chan
It's kind of a tough call what to recommend. He's a mod_perl newbie, so
I don't feel comfortable suggesting he start with mp 2 at the moment.
Ultimately the best approach is probably to write for mp 1 now, and port
it in a few years with the help of compat, but Registry is a tempting
alternative
Perrin Harkins wrote:
On Wed, 2003-10-15 at 15:13, Stas Bekman wrote:
The biggest problem with Apache::compat is that it modifies the behavior of
several methods to behave like they did in mp1. So if you run on the same
server some code that relies on their mp2 behavior, there is a conlict.
Th
On Wed, 2003-10-15 at 15:13, Stas Bekman wrote:
> The biggest problem with Apache::compat is that it modifies the behavior of
> several methods to behave like they did in mp1. So if you run on the same
> server some code that relies on their mp2 behavior, there is a conlict.
That makes sense. S
Perrin Harkins wrote:
I recently gave some advice on perlmonks.org to a person who was
concerned about what his migration path would be if he develops for
mod_perl 1 right now. I told him he will be safe if he uses
Apache::Registry, since he should be able to run his A::R scripts under
ModPerl::Re
I recently gave some advice on perlmonks.org to a person who was
concerned about what his migration path would be if he develops for
mod_perl 1 right now. I told him he will be safe if he uses
Apache::Registry, since he should be able to run his A::R scripts under
ModPerl::Registry unchanged (assu
