in reply to Threading with a twist

Boss:

I would split that boss into two threads. A dispatcher listening on <STDIN> handing of work to workers and a publisher de-queueing the results from workers and publishing them to <STDOUT>

Cheers,
R.

Pereant, qui ante nos nostra dixerunt!

Replies are listed 'Best First'.
Re^2: Threading with a twist
by Anonymous Monk on Oct 03, 2017 at 08:39 UTC
    Why?
[reply]

      Because KISS

      The design in the OP gives two very disparate jobs to the 'Boss'. It must flip between checking if there are results on the results queue and handling them, then seeing if there is anything to read on <STDIN> and passing it off to workers. The OP is talking about using non blocking calls and sleeps to do this. The complexity clearly recognised by the multiplicity of punctuation marks ... Monitor $RXQUEUE and <STDIN> - simultaneously???

      If we split these two functions then we have two simple tasks.

      • Listen on <STDIN> and put work on worker queue.
      • Listen on results queue and publish results
      both tasks can be written with blocking calls ensuring they sleep efficiently until they have work, then spring to work with alacrity when there is something to do.

      Cheers,
      R.

      Pereant, qui ante nos nostra dixerunt!
[reply]
[d/l]
[select]
        Having extra thread only for print is kiss?
[reply]

In Section Seekers of Perl Wisdom