This is case where apartment threading might be useful...

I'd suggest wrapping your socket I/O logic in its own class - kinda like a protocol stack, but I'll call it an "I/O discipline". You then run the I/O discipline object in its own thread, and the session object in its own thread, and communicate between your session object and your I/O object via a Thread::Queue (or similar facility). (Take a peek at DBIx::Threaded for a similar solution to a more complex I/O discipline)

Note that, while it is possible to pass the socket around in a fileno form, and then fdopen() it in the receiver, I think using the apt. threaded I/O discipline may be preferable, in the event you ever need to add another apartment threaded object to your app.


In reply to Re: Threaded UDP Communication by renodino
in thread Threaded UDP Communication by valhalla418

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.