I think this is the best answer so far (++). It leads to the question ... is "CGI the protocol" clunky? OR is "CGI the implentation" (fork/exec) clunky? Or is "CGI the CPAN module" clunky?

The protocol is fine.

The implementation *may* be clunky for certain classes of web applications but in your average environment (decent sized machine with reasonable user base), the fork/exec model is really not as bad as everyone thinks. 50K - 100K hits per day is not going to stress a decent setup.

As for the CPAN module. I always consider CGI to suffer from multiple personalities. The one personality is a top-notch CGI (the protocol) parameter parsing beast that should not be dismissed. The other personality is a mediocre templating system that should be avoided like the plague (IMHO). The great thing Lincoln did was create the module in such a way that using CGI for it's parameter handling features alone is possible and you're not really incurring any penalties by ignoring the HTML generation/template features.

So yes, CGI::Application combined with a decent templating system is the next logical step from a pure CGI approach.

-derby

In reply to Re^2: CGI Replacement Recommendations? by derby
in thread CGI Replacement Recommendations? by Anonymous Monk

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.