Simple solution (assuming you're just passing scalar values to your worker threads):

use Thread::Queue;

# in your "job shutdown" dispatcher:
#
#    start the worker threads, passing the $q
#
my @workers = ();
my %queues = ();
my $q;

$q = Thread::Queue->new(),
push(@workers, threads->new(\&run, $q)),
$queues{$workers[-1]->tid()} = $q
    foreach (1..$threadcount);
#
#    wait for them all to tell you they're ready
#
my $resp = $_->dequeue()
    foreach (values %queues);
#
#    now do yer thang...when you get a "shutdown event":
#
$queues{$killtid}->enqueue('Kill job');
[download]

and a stripped down worker thread:

sub run {
    my $q = shift;
    $q->enqueue('ready');
#
#  need to sleep or otherwise wait for the
#  spawner to read the queue
#
    while (1) {
        my $cmd = $q->dequeue();
#
#    process the command; you'll need to 
#    add a timer to come back and check it
#
    }
}
[download]

All that being said, if you need to pass around more complex resource objects between threads, you might consider Thread::Queue::Duplex, and make your object threads::shared, e.g.,

package WorkerResource;

use Thread::Queue::Queueable;

use base qw(Thread::Queue::Queueable);

sub new {
    my $class = shift;
    
    my %obj : shared = ();
    #
    # ...do some object init..
    #
    return bless \%obj, $class;
}
#
#    overload Thread::Queue::Queueable marshal methods
#
sub curse {
#
#    marshall any complex object members into something
#    that can be passed over a Thread::Queue::Duplex,
#    i.e., either a scalar, or a threads::shared ref
#    note that, if your object is threads::shared,
#    it implies all its members are either scalar or
#    threads::shared, so you can use the default TQQ::curse()
#    
#
}

sub redeem {
    my ($class, $obj) = @_;
#
#    unmarshall any complex object members and rebless the
#    object back into its class.
#    note that, if your object is threads::shared,
#    it implies all its members are either scalar or
#    threads::shared, so you can use the default TQQ::redeem(),
#    which just blesses
#
}

package main;

my $q = Thread::Queue::Duplex->new();
my $thread = threads->new(\&run, $q);
my $resource = WorkerResource->new();

my $msgid = $q->enqueue($resource);

my $result = $q->wait($msgid);
[download]

If the resource you're passing between threads needs read/write locking, check Thread::Resource::RWLock.

However, be careful of passing around closures and filehandles. The former just won't work; the latter needs some magic to convert to fileno's in curse() and back to handles in redeem().

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.