When I did something like this I went the completely opposite - server side storage and cookies. And I had a page for every single script. That sounds horrendeous, but it worked quite well after I made a module to include in each script. It checked cookies, connected to the database, etc. Then each cookie just contained the form validating bits, and was usually no more than 50 lines.
It also turned out to be a good idea because the client kept changing his mind on bits, and I had the flexibility to accomodate him.
Also, having done this before I would recommend keeping away from monolithic routines like that unless you really like dealing with if statements nested five or ten levels deep.
HTH, and I have a funny feeling I've seen a CPAN module to automatically handle the hidden fields thing. ovid was into this a while ago, you might want to browse through his old code posts too.
____________________
Jeremy
I didn't believe in evil until I dated it.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.