You might say CGI.pm is the emacs of web programming.
As far as I care, CGI.pm can pile whatever
it wants in there. The overhead of CGI programming is
absurd anyway. What would your mom say, you forking
perls like that? Shame! :)
For getting params, it's identical to use Apache::Request
as to use CGI.pm. The advantage of CGI.pm is its generation
of HTML elements, everyone realizes, but that itself is a no-no if you're
working with HTML designers, where you want to separate
the HTML from the Perl as much as possible.
About the LWP part, I'm kind of confused, but I guess I
never happened to use the LWP-ish parts of CGI.pm.
I think, if you only need to use the LWP-ish parts,
then definitely use LWP. Sometimes I just 'use CGI::Util'
say, if I want to URL-encode something, or CGI::Cookie.pm
for cookies (actually I would use Apache::Cookie, but anyway... :)
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.