Some tips:
  1. Sessions are not a good place to store any significant data. They are inefficient, can't be queried through SQL, and don't support concurrency safety methods like transactions. Store an ID for a shopping cart in the session, but store the actual cart data in a database.
  2. If you use MySQL, use InnoDB tables. A shopping cart system is not a silly little forum app -- you need transactional safety for this.
  3. Apache::Template is just a mod_perl handler for running files through Template Toolkit. If you are using CGI::Application, you have no use for it. You can use TT directly from CGI::Application. There's even a plugin module for it.

    In reply to Re: Code Design Issues by perrin
    in thread Code Design Issues by boboson

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


  4. Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  5. Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  6. Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  7. Please read these before you post! —
  8. Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  9. You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  10. Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  11. See Writeup Formatting Tips and other pages linked from there for more info.