Well, here is the std Perl threads tutorial http://perldoc.perl.org/perlthrtut.html .
And more MS specific http://aspn.activestate.com/ASPN/docs/ActivePerl/5.8/lib/threads.html as you'll prob be using ActiveState Perl.

I've only ever used it on Linux & Solaris, but it works fine.
You just have to be careful, especially if you've never used threads before.
Note that if you want a multi-level variable eg HoH... to be thread shared, you have to explicitly share each level as it's created.
Something I learnt from BrowserUK.
Anyway, as usual, feel free to ask qns.
It's true that officially it's not prod ready as some (or more) modules are not guaranteed 'thread-safe'. However, there are many threaded perl progs running in production.

Cheers
Chris


In reply to Re: perl multithreading by chrism01
in thread perl multithreading by spx2

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.