I'm just starting to learn about threads myself, but have you looked at the Threads modules on cpan, it looks like Thread-Tie
and Thread-Use
seems to apply to your situation. It looks like Elizabeth Mattijsen is trying to work thru alot of these issues.
From the perlthrtut:
If you're using a module that's not thread-safe for some
reason, you can protect yourself by using it from one, and
only one thread at all. If you need multiple threads to
access such a module, you can use semaphores and lots of
programming discipline to control access to it.
I guess the conventional wisdom, is if your app needs to keeps variable data separate, use a forked model. If your app needs to share variable data, use a threads model.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|