[kepler-users] Event handling, event-listener

[Maurice Yarrow]

Hello Kepler-users

I see from the documentation that Kepler supports event-listeners.
That said, then may I presume the following to be true (?):
A  Java actor may have an event-listener attached.  When receiving a
suitable event, that event may interrupt processing of the actor (a
fairly basic interrupt pattern) and cause processing to proceed
elsewhere in that actor.
(Please advise if this model is not true.)

The second issue I would like to inquire about is the following:
How do simultaneously active actors within the same workflow implement a
keep-alive-notify signal ?   I.e.: if one actor (say, actor 
A1) were to fail, how would another actor (actor A2), which was
simultaneously active, become aware of the loss of actor A1 ?
If this is possible and simply an extension of the above event-listener
capability, how is it implemented in practice ?

Third: can the Kepler workflow engine multiplex work-graph execution.
I.e.: presume two unique work-graphs, G1 and G2.
Can one Kepler engine simultaneously manage both G1and G2 ?
If so, is this activity a multiplexing or multi-threaded model ?

Lastly, is there a Javadoc for the Kepler and Ptolemy API's ?

Many thanks,
Regards

Maurice Yarrow


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mercury.nceas.ucsb.edu/ecoinformatics/pipermail/kepler-users/attachments/20051206/90aa9dee/attachment.htm