Just in case it's needed, this addendum to bv's fine reply:

No, the post data does NOT go to the command prompt. It goes to the file descriptor, STDIN, which is NOT solely a repository for data from a command prompt.

Then, if you use CGI (read perldoc CGI), you don't have to worry about the info getting to the server; your visitor's browser sends it to the file handle STDIN at the server, whence Apache or other http server programs pass it to your CGI script. The script must process the data elements thus passed and generate information for the server to act upon (generalization: pass back to the browser as a new page).

In reply to Re: stdin in perl by ww
in thread stdin in perl by manishrathi

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.