I am always of the opinion that threads and processes should terminate themselves, and that they should, where possible, “stick around, waiting for more work to do,” instead of coming into existence to service one request and then flaming-out.

The kill(9) protocol is definitely one that was “taken from Unix,” and it really does not have a good parallel in the Windows (i.e. DEC VAX 11/780...) world-view.   And yet, I have never recommended “management by the use of overwhelming deadly-force”   ;-)   anywhere.

Building process contexts, and tearing them down, are best thought of as expensive operations.   And, the maximum number of processes that may exist at one time is usually something that you want to govern.

In reply to Re: Proposal how to make modules using fork more portable by sundialsvc4
in thread Proposal how to make modules using fork more portable by Anonymous Monk

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, 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
  • 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.