Slashdot Mirror


Help Test mod_perl 2 Release Candidates

stas writes "After almost 3 years of work mod_perl 2 is almost ready for its 2.0.0 release. We plan to make the gold release in a few weeks. Please help to test the release candidates by starting to port your mod_perl 1 applications to mod_perl 2. Make sure to read the documentation and report any problems that you may have discovered. Thanks."

3 of 54 comments (clear)

  1. Is mod_perl a legacy technology? by LizardKing · · Score: 2, Interesting

    Not a troll, but something I'm genuinely wondering about - haven't things like J2EE, .Net and PHP made mod_perl obsolete? Back in the bad days of the web, the choice was C or Perl hooking directly into the Apache API to avoid spawning too many processes. Then along came Java servlets or ASP for those drawn to the dark side. Would anyone really consider mod_perl for a serious sized web application any more?

    1. Re:Is mod_perl a legacy technology? by KeyserDK · · Score: 2, Interesting

      I'm actually developing new sites with AxKit.

      --
      still reading?
    2. Re:Is mod_perl a legacy technology? by ahdeoz · · Score: 1, Interesting

      I'm thinking of switching to mod_perl, and I don't even like perl. I have alot of PHP pages that load just way too much on every request, and a lot of custom built servlet-frameworks because I don't like any of the existing java frameworks. Lately I've come to the conclusion (and reaffirmed by Rod Johnson's J2EE books) that it's really okay to put your application stack all together as long as it's logically separated. My only complaint is that it seems most of the perl knowledge is locked up in the minds of perl gurus, though I'm always amazed at what I find on CPAN when I go looking for something (recently, a EAN to ISBN converter written by a librarian in Tampa, thanks; although it took longer to install all the modules than it would have to learn how to calculate the checksum myself -- and of course CPAN broke after a few and I ended up copying several manually after their Makefile.PL choked and then I had to create a no-op module to get it to run.