[kepler-dev] about communication between director and actor

[Ming Wu]

Hi, Jianwu

In our work, each actor has its own configuration properties. and we
expect these actors configuration properties will be contained in a
global file. so we are thinking if the director can pass configuration
information into each actor, then we can let the director to extract
individual configuration properties for each actor from the global
file and pass it into the actor, instead of asking each actor to
specify its configuration information.

thanks,

Ming

On Mon, Aug 30, 2010 at 3:08 PM, Jianwu Wang <jianwu at sdsc.edu> wrote:
>  Hi Ming,
>
>    In my understanding, director can not do it since director only controls
> the invocation of actors, not sends messages.
>
>    What exact information do you want to pass? Would you please give an
> example? Maybe your requirements can be met in other ways?
>
> Best wishes
>
> Sincerely yours
>
> Jianwu Wang
> jianwu at sdsc.edu
> http://users.sdsc.edu/~jianwu/
>
> Assistant Project Scientist
> Scientific Workflow Automation Technologies (SWAT) Laboratory
> San Diego Supercomputer Center
> University of California, San Diego
> San Diego, CA, U.S.A.
>
>
> On 8/30/2010 11:29 AM, Ming Wu wrote:
>>
>> Dear All,
>>
>> I am wondering, when an actor is constructed or preinitialized, or
>> initialized, is there anyway for its director to pass into some
>> information to this actor?
>>
>> Thanks,
>>
>> Ming
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at kepler-project.org
>> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
>