I think you have the POST-redirect-GET wrong. The point is not to "avoid calling an in-memory function" (whatever that is). The point is to do whatever action you need with the posted data and then redirect the user to a different page. So that if all this goes well, the user may refresh that page as many times as he/she wants without the danger of posting the same data again and accidentally submitting yet another order or yet another posting.

If you stick all the data to the session or somewhere, redirect the user and process the data only once you receive the GET request, you've just killed any reason to do the redirection.

IMHO, of course.


In reply to Re: CGI::Prototype criticism 1 - cannot use POST-redirect-GET paradigm by Jenda
in thread CGI::Prototype criticism 1 - cannot use POST-redirect-GET paradigm by metaperl

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.