mod_perl is pretty common, and I think any site using
Perl CGI would prefer if possible to hook into mod_perl for the performance boost (by using Apache::Registry or something). If you're planning to do much web development
with Perl, it's useful to learn mod_perl. Learning
mod_perl also helps you understand how Apache itself works.
So an argument for learning mod_perl (or anything) is that the extra knowledge will help you make better decisions than if you don't know it.
However, I think HTML::Mason doesn't really require much mod_perl knowledge. It would help you understand what's going on underneath, but you could learn HTML::Mason at a
more conceptual level if you wanted. If the main reason you wouldn't learn HTML::Mason is because you're intimidated by mod_perl, I think you can eliminate that reason.
The hardest part of HTML::Mason when I first learned
it was the initial Apache configuration, but it's well documented and there's a mailing list to read archives
or ask questions.
Typically with HTML::Mason, you put HTML at the top
of a template page and some Perl at the bottom.
The HTML will have special tags in it, similar to JSP
or ASP. Then below it, you'll put some
Perl code to initialize variables. But I think the powerful
thing about HTML::Mason is its "object-orientedness".
You can use "autohandlers" to automatically produce
parts of the pages, and you can use "methods" that
are object-oriented so you can override them and whatnot.
I guess in the end it might be just what fits best
with your style, so maybe HTML::Template or Template
Toolkit makes more sense for you. But knowing mod_perl will still be useful anyway.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
