Neither will use enough to matter. I can make a case both ways and would be that it varies more between servers than it does between cases. POST sends a little more data but putting the data in a header eases the burden of parsing the data. POST creates a buffer for the STDIN pipe but GET burdens the Environment of the shell.

My advice? Spare your users the ugly URLs and use POST. If that advice falls on deaf ears, then I recommend you use the one you are more comfortable with. Your time is more valuable than 10 times the server resources you would ever save.

And if you use Perl, for goodness sakes use CGI; is your friend. Then you can use either and it will work just the same. (well, unless you move more than 8 or 16 KB of data or need file uploads, then POST is your only rational choice.)

--
$you = new YOU;
honk() if $you->love(perl)

In reply to Re: Post vs. Get by extremely
in thread Post vs. Get by Anonymous Monk

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.