In my CGI/Mod Perl applications I use an action variable to direct my program to do what needs to be done. i.e.
A few more things:
  • How come the submit button(s) of the form isn't enough to decide what to donext? That, in conjunction with HTTP_REFERER are enough in most cases. It keeps your dispatch table down to do dimensions. One dimension is the value of the action and the other is the value of the REFERER.
  • I wonder why you had to present such an unrealistic example in your initial post. Can you supply us with a real-word example of your case-based form dispatch?

    In reply to Re: CGI/Mod Perl Application Design philosophy - which way do we go? by princepawn
    in thread CGI/Mod Perl Application Design philosophy - which way do we go? by BMaximus

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • 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
  • 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;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.