Hi, everyone. I've got this setup: a thread that receives a udp multicast message and sticks it into a 3D hash ($foo{$bar}{$blah}). Then I've got main() that goes through the hash and does processing. The problem is sharing %foo between main and the thread. As I'm sure you know, ::shared is not allowed. What do I do? I tried using Thread::Queue but that doesn't work (prob because I'm using "use threads", as per perlthrtut. I need something simple that will let me enqueue a hash (or anything, really -- I could enqueue an unformatted udp msg and hash it upon dequeuing.) Multicast msgs arrive fast and furious and my receive thread can't do anything except pick it up off the wire, shove it some place and move onto the next msg, for fear of losing updates. Thank you all!

In reply to sharing a hash of hashes between threads by coontie

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.