Yes, that would be a great approach, and here is why:
If you aren't passing that data back and forth with every apache server interaction, you do not make that data vulnerable to the threats of form cracking or man-in-the-middle sniffing.

As I recall, CGI::Session handles this out of the box, but the primary vulnerabilities left becomes cracking your session ID and injecting bad data through th form fields. Don't make your session IDs sequential or otherwise easily guessable and you protect your application and your users from that threat, as well. As for the injection of bad data, FormValidator is useful.

-- Hugh

if( $lal && $lol ) { $life++; }

In reply to Re: CGI Session instead of using hidden variables by hesco
in thread CGI Session instead of using hidden variables by stumbler

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.