On Mar 20, 2009, at 17:21 , Peter Soetens wrote:

> On Monday 16 March 2009 16:44:59 S Roderick wrote:
>> Looks like I might be needing this functionality ...
>>
>> What is the current status of events over CORBA? What is currently
>> preventing this? How far did the work progress?
>
> It got on the todo-list for RTT 2.0 because that's the only setting
> in which
> it looks doable. You have to understand that each part of the event
> interface
> must be transportable over CORBA. Today, it's too much dependent on
> template
> code and too complex to transparently support. RTT 2.0 will solve this
> elegantly, by allowing methods and messages objects to attach to
> events, which
> have representations in the CORBA interface as well.
>
>> It looks like I'll just need transport of an event from a state
>> machine in one deployer, to the state machine of another deployer.
>> The
>> event won't carry any data/parameters with it. If I have to, I can
>> most likely workaround the issue using method/command calls but
>> events
>> would be the far cleaner solution.
>
> I recommend this work around for now. To have a bit of the 'event'
> feel, you
> could let all peers that need to react to the event have a common
> method
> defined and let the event raiser scan it's peer list for that method
> (by name).
> When the event is raised, it then calls all these methods.

Implemented a similar workaround with states-on-ports and methods.
Works for now.

Looking forward to the RTT2.0 functionality! :-)
S