Simplistically, put the functions in a thread also. That also allows your select loop to remain responsive to other comings and goings.

Of course, then you need to track what threads you've started on behalf of what clients. and that starts to complicate things a bit. You could have the function threads connect back to the listener to return results, but depending upon how many clients you have it could get expensive spawning threads for short processes.

A better architecture, especially with ithreads, would be to have your longer running functions run in long-running threads with loops reading from function specific queues and writing back to a shared results queue for dispatch. The select loop uses a timeout and monitors the results queue using dequeue_nb().

That's harder to describe than write, but if the tachnique interests you I could probably adapt your example to demonstrate it?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^3: Printing to all clients on a socket from a child process by BrowserUk
in thread Printing to all clients on a socket from a child process by Fredde87

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.