I am happy again to announce the release of the next Ninject extension, Ninject.Extensions.MessageBroker 2.0! You can download the release from GitHub for all supported platforms (.NET 3.5, .NETCF 3.5, SL2, SL3, MONO). Also, you can review the demo post using the extension if you are wondering how to hook it together.
Contact
Badges
GitHub- idavis pushed to master at ninject/ninject June 24, 2010 idavis
- idavis pushed to master at ninject/ninject.extensions.conventions June 18, 2010 idavis
- idavis started following remogloor June 18, 2010 idavis
- idavis edited a page in the ninject/ninject wiki June 13, 2010 idavis
- idavis updated gist: 433641 June 10, 2010 idavis
{ 5 comments }
In what scenarios do you envision using a message broker like this as opposed to JMS/NMS or MSMQ? Besides lack of features, of course
I used it to implement a MVP pattern application to hook the view and presenter together and also to deliver messages to extensions.
Funny, cuz that was that exact situation I may be able to use this. I currently use a an observer pattern to do this in an MVP app, where the main presenter notifies each sub presenter of a state change. Semantics aside, it is the pretty much the same thing. Had this been released a week or two earlier, I might have used it instead
This is pretty much a light weight, non-distributed messaging API…cool!
I actually prefer the WeakEventMessageBroker extension myself. I hated the WeakEvent pattern put into the presentation framework, so I built my own. It doesn't have the delivery options like thread and UI yet, but it using weak pointers for publishing and subscribing detaching the event handling from the object lifetime. The channels and objects clean themselves up nicely.
Cool, i'll check that extension out.