On Thu, 3 Dec 2009 22:37:37 +0800
Ryan Chan wrote:
> On Wed, Dec 2, 2009 at 2:56 PM, Nick Perez
> wrote:
> > On Wed, 2 Dec 2009 12:42:34 +0800
> > Ryan Chan wrote:
> >
> >> If I goes with the fork solution, any abstraction recommended?
> >
> >
> > I don't want to scare you off, but I can also s
On Wed, Dec 2, 2009 at 2:56 PM, Nick Perez wrote:
> On Wed, 2 Dec 2009 12:42:34 +0800
> Ryan Chan wrote:
>
>> If I goes with the fork solution, any abstraction recommended?
>
>
> I don't want to scare you off, but I can also suggest POEx::WorkerPool.
>
> --
unfortunately, make failed in CPAN in
On Wed, 2 Dec 2009 12:42:34 +0800
Ryan Chan wrote:
> If I goes with the fork solution, any abstraction recommended?
I don't want to scare you off, but I can also suggest POEx::WorkerPool.
--
Nicholas Perez
XMPP/Email: n...@nickandperla.net
http://search.cpan.org/~nperez/
http://github.com/np
On Wed, Dec 2, 2009 at 5:31 AM, Rocco Caputo wrote:
> The other general advice is to use fork(), with or without POE, when you
> need true parallelism.
>
It seems POE::Component::Pool::Thread can solve the problem? (But I
was unable to install via CPAN in ubuntu)
If I goes with the fork solution
The other general advice is to use fork(), with or without POE, when
you need true parallelism.
--
Rocco Caputo - rcap...@pobox.com
On Dec 1, 2009, at 08:50, Mark Morgan wrote:
Good day, Ryan,
The problem with using 'sleep' in POE code is that POE isn't true
pre-emptive multi-tasking, but
Good day, Ryan,
The problem with using 'sleep' in POE code is that POE isn't true
pre-emptive multi-tasking, but rather cooperative multitasking at the
process level. Different sessions are still running in the same
process/thread, so any actions that will monopolize CPU time for a
stretch will b
Hello,
Consider my code below would like to execute the sleep() function in
parallel, using POE JobQueue component:
#=
use strict;
use POE qw(Component::JobQueue);
# Passive queue waits for enqueue events.
POE::Component::JobQueue->spawn(
Alias => 'passive',
Wo
