EventBus

[Duncan Child]

Does anyone know why the event bus also has a Manager and a ManagerFactory?

Any objections to switching it to be one class called EventBus that
has static methods for

publish
subscribe
unsubscribe

and a bunch of static final strings for common event names.

Thanks

Duncan

[Dan Dromereschi]

Duncan,

The changes you propose can be done, but I had some reasons in doing that design at that moment: I was thinking that maybe the event bus might have at some moment several implementations, so this is why there is an IEventBusManager and the implementation(s) for it is (are) hidden behind this interface. This way, the factory would be needed to return the correct implementation, based on some eventual parameters.

If we are sure this feature will never grow bigger than it is, we can safely transform the factory into a single class with static methods.

Regards,

Dan

[Duncan Child]

Hi Dan,

Thanks for the response. I understand what you did now and can see
why. I just checked in something simpler that should be sufficient for
now.

Thanks

Duncan