> Greetings,
> 
> While reading some of the Perl newsgroups, I've seen a few examples of
> people getting CGI parameters by either parsing the query-string (for
GETs)
> or reading in some of the content (for POSTs). I've been working with CGI
> (using Perl) for a little while now and I've always used the param()
method
> in
> CGI.pm and it is working for both GETs and POSTs. I'm wondering if I'm
> missing something and if there are times when using the CGI.pm param()
> method is not advised. Thanks.
> 

You're not the one missing out.  'param' specifically isn't always the
best way, for instance sometimes I like to pull them all at once with
the 'Vars' method.  Or in the case of file uploads I generally use the
newer upload interface methods.  Point being, you should rarely if ever
need to parse the query string/post yourself.  To me, using the CGI
module would never be the wrong way to do it, whereas the other would
be.  mod_perl not in consideration at this point, aka there is the
Apache::Request (I think?) for that, etc.

http://danconia.org


-- 
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>


Reply via email to