Events, EventManager & EventAggregator

Coordinator
Jan 12, 2010 at 10:16 PM

David Mora: Although we have several specialized types of events, the event manager would be oblivious to them. We would have a base class or interface from which all events derive or implement. Right? The event manager will then act as a proxy service between publishers and subscribers. Someone raises an event by telling the manager to do so (as you mention), and the event is broadcast to the all the subscribers. The publisher never knows who is listening to the events. (That is the architecture of PRISMs Event Aggregator.)

 

Jesse: Yes, that is my hope. I don't know, given that loading modules is order-independent if there are any events that the eventManager must be born knowing, but I don't think so.