Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • FWIW: not all Perl servers are single threaded: HTTP::Daemon::Threaded [cpan.org] was recently loaded to CPAN. Its pretty green (simplistic session mgmt, no DBI connection pools - yet), and isn't really intended for large scale performance, but rather for simple integration into web-enabled apps. But it might be interesting to see how well it can scale (ie, how many threads can be managed).

    I'm currently using it to develop a debugger [presicient.com] (very prelim view), hopefully that will shake out HTTP::D::T a bit more.

    BTW: does

    • I think Brian Mosely has left the building. He used to be on the mod_perl list, but we haven't heard from him in years. I'd steer clear of Servlet at this point.
  • One thing I find interesting is that the new web servers are being used because of bugs in the older ones. Lighttpd + FastCGI is popular partially because mod_fastcgi on Apache 2 has issues. Instead of fixing the bugs or using mod_fcgid, people switched platforms. And mod_ruby does exist but I don't know why people don't use it for Rubys on Rails.
    • The Ruby people pushing for Mongrel were fleeing Lighttpd and FastCGI, which they claim is buggy.
  • You've got a pretty big vested interest in Apache/mod_perl, and while I did previously, I don't any more. I have to be honest in that writing AxKit2 this way was mostly because I was curious as to how good it could be. I know pretty much for a fact that it'll be slower than mod_perl, because Apache2's connection handling and perl integration is very well built and designed.

    However now AxKit2 is built I find it much easier to hack on than mod_perl, and not just because I know the internals. Adding a new conf
    • Adding config stuff was pretty bad in mod_perl 1. It's supposedly easy in mod_perl 2, but I've never wanted to add a config directive so it's not something I pay attention to. I really don't use any of the Perl config stuff in mod_perl at all. It just doesn't appeal to me.

      Profiling, quick restarts -- well, they work for me in mod_perl. (This reminds me of working at a place that used IBM WebSphere, where restarting the dev tools to pick up a code change took 10 minutes! What a pig that thing was.)

      You

      • I think partly people don't add custom config in mod_perl apps because they're hard (still non-trivial in mod_perl2 - that was one of my stumbling blocks in doing a straight AxKit port to mp2), and partly because they are satisfied with "PerlSetVar" which I never really liked as it didn't seem to cope with multivalues terribly well, and partly because none of the introductory docs cover them. I've tried to make sure my introductory docs jump right into them because they're terribly useful.

        Another option I'm