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."
Btw, php does not make mod_perl obsolete. Yes, php can be hosted in a lesser secure area, as php scripts assume the user its running as, but that's about it. It's an ugly language full of redundancy, bugs and inconsistent style. j2ee and
Biggest problem with php, is their "modules" are c-compiled. There is the least portability with it. With perl, perl written modules, not the XS modules, can be easily copied anywhere. j2ee not so much, as the configuration files change format from server to server. But from os to os, they are the same.
-
ping -f 255.255.255.255 # if only
The Register uses Bricolage, a content management system written with Mason, a mod_perl application. It's a bit of a stack, but it works good.
Remember also that under Windows AP2/MP2 is the only stable option currently available.
:-)
Personally I have been using MP2 in production on windows for well over a year - call me an early adopter
FYI the only problem the windows install has ATM is the a bug that took from perl5.8.3 to perl5.8.6 to fix.
On the linux side the benefit of the reduced memory profile and increase in performance we have seen is enough to migrate new installations to AP2/MP2. We have yet to have a problem on the Linux side and no longer see swapping.
Stas and the team overloaded the Apache:: namespace to make MP1 to MP2 migration easier.
Why no one perlish (including myself or randall) complained at the time is inexcusable.
I should have spotted this problem then and for that I apologise to Stas and the team.
Regarding not using AP2/MP2 I think that this will (hopefully) have little effect.
The windows folks use PPM's which do not rely on PAUSE/CPAN model.
On the linux side AP2/MP2 tends to be the choice of commercial distributions.
Getting people to step back down the ladder because even more stuff can no longer be found on CPAN will hopefully not happen.
Personally rather than backbiting we should be trying to extend CPAN to cover the more generic problem of external dependencies, rather that trying to ignore it or assign blame.
After all perl interfaces to a lot of systems and I do not want to see versioned namespaces such as ApacheN XML2 etc for even more external dependancies.
Jacqui dot Caren
at
mymail.aixx.com
mod_perl, and to a certain extent Java servlets, gives you a huge amount of power over the web serving process, and are suitable for developing web applications that can do almost anything with HTTP. (emph. mine)
even as you attempt to broaden the sense that mod_perl is more than just some content generating script, you undermind the essence of what you talk about.
mod_perl is capable of being used to write entirely different protocol handlers: you can make apache serve FTP or ssh with mod_perl, if you're insane enough to do so. it can completely alter the flow of information at any step in the proces, thanks to apache's beautiful filtering & module structuing.
as you state, mod_perl uses the apachi api to tie itself deeply into the apache server engine itself, performing all sorts of reconfiguration of apache. `tis truly divine.
I don't see why they wouldn't. I really think it comes down to what best fits your situation and what skills you have. I think PHP is great and I'm a casual programmer but I think the lack of namespaces can be super confusing in large projects. I've used Perl and its got tons of features and mod_perl is incredibly fast but its to say the least confusing. .NET is stuck to MS servers to the most part. Its just using what works best for you.