Re^2: Boolean Thread::Semaphore ?

You don't want a semaphore.

The simplest mechanism is:
while( my $workitem = sourceOfWork() ) {
    sleep 1 while $Q->pending > MAXQ;
    $Q->enqueue( $workitem );
}
[download]

Thanks, that looks to be a much more sensible approach compared with what I was doing with semaphores.

That should teach me to read algorithoms online that are intened for other languages or problem domains where near realtime responses are required.

Comment on Re^2: Boolean Thread::Semaphore ? Download Code

Replies are listed 'Best First'.
Re^3: Boolean Thread::Semaphore ? by mellon85 (Monk) on Feb 08, 2012 at 17:28 UTC
The best way (aka not polling) would be that the worker thread will stop itself if the queue is full, and will be restarted by a client thread by a signal. take a look at thread signalling chapter in threads documentation	[reply]
Re^4: Boolean Thread::Semaphore ? by BrowserUk (Patriarch) on Feb 08, 2012 at 19:00 UTC
take a look at thread signalling chapter in threads documentation That is a truly awful idea. Try it for yourself to find out why. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]