-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge EventAggregator and MessageBus #4
Comments
It sounds like it could be interesting, yes. I'll have a look at it. |
I have been looking into this, but I have some doubts. While I do understand the general idea, I'm not sure I see the real benefit here. Wouldn't you better off chosing one or the other? Do you have an example where you would actually "need" both? Or is it just to be able to make the transition from one to the other or use code that cannot be changed? |
Yes you would be better off choosing one, and you don't need it. I was thinking mainly for legacy projects where you've started with one, and want to swap to the other. Currently I have an existing Caliburn.Micro project with ReactiveUI being the new thing. Lots of old style IHandles mixed in with new MessageBus. Ultimately this would be cool to have, so you won't have a problem if you mix the two. But if it's hard it doesn't have to be a high priority. |
@distantcam Is it still something you would find useful? |
Useful, yes. But I'm not sure how useful. In the end I tended to just pick one or the other. |
It would be really cool if these two items were merged. Currently if you fire an event on one the other doesn't know about it, and vice versa.
The text was updated successfully, but these errors were encountered: