The process has a STDIN, STDOUT, STDERR, and the FastCGI protocol essentially works from that and nothing more.
That is wrong!
What you've described is (or at least comes closest to being) CGI.
The FastCGI protocol explicitly doesn't use STDOUT & STDERR; and whilst STDIN is open, it explicitly isn't the normal STDIN; and is in fact only an alias to something else.
And you have the gall to "cordially suggest" to flexvault.
More, pointless, meaningless, malignant and destructive garbage delivered so "politely" that it persuades other know-nothings that you're being oppressed.
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.