[kepler-users] Wireless channels across Case actor

[cxh at eecs.berkeley.edu]

HI Bob,
The short answer is that there is no way to tunnel wireless  connections
to and from the Case Refinements.  Edward Lee might have some input
here.

The longer answer is that the each case of the Case Actor requires
a director. The fire() method of the CaseDirector describes part of
the reason why:

--start--
     *  Schedule a firing of the given actor at the given time.
     *  If there is an executive director, this method delegates to it.
     *  Otherwise, it sets its own notion of current time to that
     *  specified in the argument. The reason for this is to enable
     *  Case to be a top-level actor and to support the design pattern
     *  where a director requests a refiring at the next time it wishes
     *  to be awakened, just prior to returning from fire(). DEDirector,
     *  for example, does that, as does the SDFDirector if the period
     *  parameter is set.
--end--

The fact that Publisher/Subscriber work across boundaries between directors
is a recent change, see
https://chess.eecs.berkeley.edu/bugzilla/show_bug.cgi?id=165

Level Crossing links are much like global variables or goto statements.

I'm not sure about your "Many-to-one" issue.  Do you have multiple
actors are are producing data and you want one actor to read the data?

Could you do a merge?

_Christopher

> Each "refinement" in a Case actor requires its own Director which seems to
> interfere with making connections using a Wireless channel established at
> the level of a model's container. Is there a way to tunnel Wireless
> connections to and from the Case refinements? The Publisher/Subscribe
> connection works across a Case actor but I need the sort of Many-to-One
> connectivity that the Wireless communication channels afford.
>
> Thanks,
> Bob Weber
> _______________________________________________
> Kepler-users mailing list
> Kepler-users at kepler-project.org
> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
>