Re: Handling Dynamic Children (Workers) without restarting the poe ikc server

Thanks so much for the info.  Yeah, I was just reading the docs when I saw
this response.  In the docs I saw this example

POE::Component::IKC::Client->spawn(
            port=>31337, name=>$name,
            subscribe=>[qw(poe://*/timeserver)],
            on_connect=>\&create_me,
        );


Is there some sort of unpublish event if the worker goes away(crashes,
etc...)?  Would I have to code this into the server logic or it's already
built in?

On Tue, Apr 21, 2009 at 1:00 PM, Nick Perez <[email protected]> wrote:

> If you read the docs for IKC you will see that it describes the publish
> subscribe mechanism implemented for remote/local session subscription.
> So basically, client would connect, subscribe to the server session,
> publish its worker session, then post() an event to the server that
> would then tell the server to subscribe to your published session. Then
> the server can access it like a local session. I am guessing you need
> to invert your thinking. The workers do the connecting. The server just
> listens. Then when a test needs to be run, the server will then post()
> an event to which ever worker it choses.
>
> On Tue, 21 Apr 2009 12:39:57 -0700
> Josh803316 <[email protected]> wrote:
>
> > If I have a POE control server that manages multiple workers using
> > IKC to communicate, how would I handle adding another worker to the
> > group dynamically.  I'm trying to create a plug and play type
> > environment where I could potentially add a new worker module to the
> > group of managed workers without restarting the server.
>
>
> --
>
> Nicholas Perez
> XMPP/Email: [email protected]
> http://search.cpan.org/~nperez/ <http://search.cpan.org/%7Enperez/>
> http://github.com/nperez
>