Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??

Excellent comments, BrowserUK.   Very informative.

My take on the matter is that, “if you are killing threads or processes, or giving up time slices, you’re going about it the wrong way.”   The timing of threads/processes is and must be completely unpredictable.   Furthermore, the things that they do are things that they need to be able to finish doing.   Instead of being “killed,” they should be “informed that it is now time for them to please roll over and die.”   Therefore, the consistently best and most-stable arrangement, I think, is to construct persistent threads (designed to handle many units of work in their lifetime), and to connect them with flexible hoses ... i.e. IPC queues.   Control the system with messages.   Indicate that it’s time to die with a shared flag, and also send a message to that effect so that any thread that’s listening on a queue will wake up, read it, put its own house in order, and die.   You can reliably implement this protocol on any system, using existing CPAN packages, thereby neatly eliding yourself out of the entire cross-platform question.   Somebody else has already done it for you.   Timing problems are eliminated by adopting a better and more rugged design.

“When faced with an edge-case, do the smart thing ... stay away from the edge.   Looks like it’s a long way down.”


In reply to Re: Threads and signals in Windows by sundialsvc4
in thread Threads and signals in Windows by bojinlund

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!
  • 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
  • Outside of code tags, you may need to use entities for some characters:
            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.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others imbibing at the Monastery: (17)
    As of 2014-07-10 19:00 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      When choosing user names for websites, I prefer to use:








      Results (215 votes), past polls