For once the questionable anonymonk is actually right: the problems do not start immediately, but over time you can accumulate multiple different frameworks into the larger application. Unless you have full management buy-in that all future work on the application is to use framework X, do not think that you are starting an "incremental" conversion to move the application to framework X. That way lies the madness of an application with parts in framework A, parts in framework C, parts in framework X, parts in framework R, and an unmaintainable mess on the whole.

You can still use newer modules like Template for newer features, especially if you can rally support for refactoring the existing code to also use Template, which will help set you up for a later move all-at-once to a more modern framework, after a destination framework is chosen. Right now, your application uses the (very minimalist) "CGI" framework and you should not take changing that lightly unless you know that you will be able to change the entire application to a new framework. Multi-framework applications are maintainability nightmares.

In reply to Re^3: Adding to legacy application: does it make sense to use PSGI in CGI mode by jcb
in thread Adding to legacy application: does it make sense to use PSGI in CGI mode by hotpelmen

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.