Nick,
I definitely think it might be simpler...
I was hoping to be able to control the workers spawing on startup based on a
passed list. I was also hoping that I could spawn a remote client to do
some load sharing in the future. I would prefer to manage it all from the
server startup. New clie
On Tue, 5 May 2009 15:54:13 -0700
Josh803316 wrote:
> Yes, thanks to some members of the list I have been taught that this
> is indeed correct and not a bug. Makes more sense now.
>
> I was trying to spawn a worker child but wasn't spawning it correctly
> therefore the process was indeed inside
Yes, thanks to some members of the list I have been taught that this is
indeed correct and not a bug. Makes more sense now.
I was trying to spawn a worker child but wasn't spawning it correctly
therefore the process was indeed inside the same kernel. I'm now using a
wheel::run to spawn the child
On Tue, 5 May 2009 10:34:53 -0700
Josh803316 wrote:
> It appears that if you start an IKC server and then an ikc client
> connects to it from within the same POE::Kernel->run() then we get
> the following error:
>
> 23289: Remote kernel 'host.domain-4a0076da5af9' already exists
> 23289: Remo
It appears that if you start an IKC server and then an ikc client connects
to it from within the same POE::Kernel->run() then we get the following
error:
23289: Remote kernel 'host.domain-4a0076da5af9' already exists
23289: Remote kernel 'host.domain-4a0076da5af9' already exists
Single pr
