Also, if the work to be done is “substantial,” you might not want to implement it in the CGI script at all, for various reasons. Instead, you might conceive of the CGI script strictly as a user-interface, in which you can queue work-requests (say, they're written to a database table), observe the completion status of requests you've queued, and retrieve the results selectively. Meanwhile, a back-end processor or processors, say written in Perl, poll this queue and carry out the work. (They put the results in a directory that’s mutually accessible and note in the database where they put it.) Now, the CGI system is back to doing what it customarily does: handling very brief, “get in then get out in a few milliseconds” requests. The worker-bee daemons can be anywhere. And results, once generated, can be viewed more than one time at will. How you devise the daemons to work, <i.e. forking or not, is entirely up to you and no longer of any concern to CGI.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||