There are really two aspects to that question, which can and should be dealt with separately:
-
There are many web-servers out there (including tiny Perl programs...), and many ways to deploy apps on those servers (FastCGI, mod_perl, etc.) It is highly desirable to be able to switch horses in mid-stream; hence the benefits of software-interface layers such as Plack. (“Design your app for Plack, and you can reconfigure Plack without having highly-pervasive changes in your application.”)
-
Within the application itself, there is usually “a whole lot of treasure-chest and only a little treasure.” The chest is basically the same no matter what goes inside, so obtain a suitable chest “off the shelf.” Hence application frameworks, such as Catalyst (and dozens of others). Always try to avoid doing something that has already been done. You want to be able to confine your interests strictly to what is actually different about your application.
This approach has a subtle added benefit: it introduces a disciplined, and somewhat distant, perspective upon your own work.
-
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.
|
