The architectural concept came from trying to add a layer of abstraction between the interface and the workers. I'd like all GUI events filtered through a boss prior to being delegated appropriately and all threads reporting results to the boss so they don't need to have any visualization coupling. The final application I'm working toward (in a very long-term sense) is complex curve-fitting and visualization in chemical engineering, with poss. Given the individual complexity of each task, I want a clear bulkhead between the two sides.

That means you are absolutely correct in saying

this conflation of loops was some attempt to bring all the interaction, input and output, together into a single thread
My intent was to perform most message passing by way of queues and use thread signaling for tasks that don't lend themselves to that approach. If the general concept (as contrasted with implementation) is flawed, I love to get set straight. This literally represents my first attempts to use threaded Perl, where I have a reasonable parallel computing background in MPI and OpenMP for scientific Fortran 9x.

Thanks for the help, insight and homework.

In reply to Re^4: threads on Windows by kennethk
in thread threads on Windows by kennethk

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!
  • 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, details, 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, summary, 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.