[Embedlets-dev] Re: [ Andrzej Jan Taramina ] Event Manager

[Gregg G. W. <gr...@sk...>]

>The only thing I think I would do differently is to keep the <producers> 
>and/or <consumer> critera out of the topic string, since this would allow 
>for much more efficient filtering on the part of the Event Manager 
>without adding much in the way of complexity for the developer. 

control.switch.*.1.<

specifies the limit of processing level in the hierarchy...  This allows 
information to be excluded from the match when it is not important.  Thus, the 
hierarchy of the topic tree goes from least specific to most specific 
information to aid in providing convienent cutoff points.

>Conceptually, it also keeps things a touch clearer since who produced (or 
>should be allowed to consume an event) is not really part of the event 
>type (or topic).

But, it can be important for debugging event traffic through the system.  And 
since it is a broadcast mesh, you can connect external monitoring to the space 
to watch what is happening without having to instrument the system internally.

>> I do have a broadcast 'space' that includes single copy delivery in a mesh
>> environment, and topic based pub/sub, that I am willing to 'donate' to the
>> cause...
>
>Is this a JINI space?

No, it is a space modeled after the Object Space voyager space.  I used 
voyager off and on in different pet projects for some time.  But, it had 
certain problems due to its design.   So I took the parts of their API that I 
used most, and wrote a new implementation without those problems, and some 
optimizations.

-----
gr...@cy...  (Cyte Technologies Inc)