Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
You say that:
It is a rather simple thing using CGI.pm, some database connections and scary amounts of print-statements.

If you have a simple thing to start with then keep it that way. Only go for the complications if you really need them. It is an excellent idea to pull out all those print statements and stick them in a template, and CGI::Application is a great starting point.

It may not be what you had in mind but I tend to add another 'layer' between CGI::Application and the actual module that generates the page - usually called something like MyApp::Base. In this I then add all those functions that crop up like connecting to the database, getting the user or redirecting to a login page (using cgiapp_init or cgiapp_prerun) etc.

This can generate some really compact and easy to test code - which can also be run on everything from a cut down CGI only server through to a full mod_perl optimised one. This last point is a real clincher - it is great having a super-dooper speedy custom setup until the server dies and you need it running now on that server there, yes the one we used as a doorstop.

--tidiness is the memory loss of environmental mnemonics


In reply to Re: Multi tiered web applications in Perl by EvdB
in thread Multi tiered web applications in Perl by pernod

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others having a coffee break in the Monastery: (6)
As of 2024-03-28 22:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found