Beefy Boxes and Bandwidth Generously Provided by pair Networks
Keep It Simple, Stupid

Comment on

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

The key design-thought to keep in mind ... in any language, in any situation ... is that “a thread or process is a hamburger cook, not a single hamburger.”   Each thread goes through the same life-cycle as does any cook in a burger-joint:   wait for an order, cook it, deliver it, and then wait for another one.   And, at the end of the shift, he comes out alive.   Maybe he cooked two hamburgers that day ... maybe he cooked a hundred.

Often, threads are specialists ... the “burger-meister,” the “fry guy” and so on.   They sit at one station, and listen to one queue.   Or they can be generalists, all grabbing from one queue and doing whatever comes.   Perl provides plenty of reliable “thread-safe queues,” and even complete workload-management systems like POE.   Your choice.

But, whatever it is, it ought to make sense if mapped to a real-world situation like a fast food restaurant.   Don’t ask the operating system’s thread/process dispatcher to dispatch your application’s work flow, because it can’t.   The so-called “flaming arrow approach” does not work in practice.   A pool of specialized or generalized worker-bees carry out the work, and live to tell the tale.

It is certainly a viable approach to structure the system so that Perl Objects are placed on the queue and the only thing that the worker-bee actually does is to call some execute() method implemented (in the abstract ...) by the base class.

In reply to Re: How do I queue perl subroutines to a thread queue instead of data? by sundialsvc4
in thread How do I queue perl subroutines to a thread queue instead of data? by static0verdrive

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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others surveying the Monastery: (3)
    As of 2018-05-26 20:29 GMT
    Find Nodes?
      Voting Booth?