http://qs1969.pair.com?node_id=738347


in reply to Re^2: What is mod_perlite?
in thread What is mod_perlite?

It would let you put perl code into your HTML files,

Where do you get that from? You can of course already do this today (assuming you use a module like Template::Toolkit or Mason), but that has nothing to do with the Apache module backend, it's a language feature. I don't believe mod_perlite has anything to do with templating.

One of the reasons (I think, this is far from my main area of expertise) that mod_php offers better performance than CGI is the fact that things Perl has as modules (e.g. database drivers) are compiled into mod_php itself (that also makes mod_php a pain to install on less popular platforms, but that's not my point). So one thing that may improve performance would be to load modules at Apache startup time (which, as perrin pointed out, you can do in mod_perl and FastCGI), but I don't see that as being a major design goal of mod_perlite. And since their approach is to reinitialise the perl interpreter on every request they would conceivably also have to reload modules, thus removing much of the benefit.


All dogma is stupid.

Replies are listed 'Best First'.
Re^4: What is mod_perlite?
by Anonymous Monk on Jan 27, 2009 at 02:20 UTC
    It would let you put perl code into your HTML files,
    Where do you get that from?

    Well, that's the whole point. It's supposed to be dirt-simple for the web developer to use and deploy, and it doesn't get any simpler than having an html file with a little bit of perl spliced into it that gets run when you use your browser to ask to see the file. It also needs to be nearly foolproof for the average sysadmin to deploy with their apache (my understanding is that this would rule out mod_perl).

    Regarding what's compiled into or not compiled into mod_perlite, or what modules are loaded when: those are implementation issues that will probably be worked out later. Sure, it would be great if mod_perlite only reloaded modules if they've been changed. That sounds like a feature that will come later.

      Hello, whoever you are :-)

      scorpio17 wrote:
      It would let you put perl code into your HTML files,
      I wrote
      Where do you get that from?
      Anonymous Monk wrote:
      Well, that's the whole point. It's supposed to be dirt-simple for the web developer to use and deploy, and it doesn't get any simpler than having an html file with a little bit of perl...

      With all due respect, I was not asking what you thought would be easiest for web developers. I was asking where did scorpio17 (and apparently you) get the idea that mod_perlite would act as a templating engine and allow you to freely place Perl code within an HTML document. None of the things I've read about mod_perlite talk about such a feature and I do not believe it is intended to do that (as said before, you can almost certainly get mod_perlite to do this by using Template::Toolkit or HTML::Mason or the like, but that would be a feature of these modules, not mod_perlite).

      As for the rest of your post, I am still waiting to hear about a single feature that mod_perlite has which existing solutions don't.


      All dogma is stupid.
        I was asking where did scorpio17 (and apparently you) get the idea that mod_perlite would act as a templating engine and allow you to freely place Perl code within an HTML document.

        Sorry. Good question. I was making a rather reckless assumption based on how easy it is to deploy php files and based on the notion of making things as easy as possible for users. I don't have any idea what deployment model the mod_perlites have in mind.

        That said, I'll add that, IMO, if you make things any harder at all than php -- even if it's just a little more work -- it'll just be thrown in your face that php is in fact still easier.