why? what's wrong w/using param? you can always parse the query string directly but that kinda defeats the purpose of using CGI ;)
You can also use some other framework like Mason or any one of the many others, but that's a pretty drastic change (but then again, we don't know why you're asking).
| [reply] |
Please explain why param() doesn't do what you want, there may be a variety of ways of doing this which may or may not be suitable to your purpose.
/J\
| [reply]
[d/l] |
The param() method also has a number of hidden benefits - many other modules that are designed to work in the CGI environment implement an interface to the param() method, thus reducing the need for you to code these interfaces.
Additionally, the param() method will return an array where it makes sense to do so, like a multiple selection or a set of checkboxes.
As somebody else said, "tell us why" because many of us have been around long enough to realise that using CGI.pm is a very safe, very robust way of handling form data. In twelve years of writing CGI scripts, since I discovered CGI.pm I have never found a reason that I could not use the param() method. jdtoronto | [reply] |
The CGI module is fine, but there are lighter-weight modules out there. CGI::Simple boasts full compliance with CGI.pm.
| [reply] |
You can read POST variables from STDIN
# read POST data from STDIN
read STDIN, $temp, $ENV{'CONTENT_LENGTH'};
Tobin | [reply]
[d/l] |
