In this short series of articles I’ll cover what MVVM is and how to use it in practice, how to solve issues when applying this pattern and how to take advantage from it.
In the previous article we discussed what MVVM is and why it matters. In this article we’ll try to benefit from the pattern and talk about the issues you have to battle through when working with MVVM. Our sample application was able to pull some data from a model, and display it on the screen in a master-detail fashion.
Without going into too many details as I'd break some contractual obligations, I can say that we needed a way for two Silverlight applications to communicate in a master/slave scenario. Typical messaging loads were in the region of around 1000 messages a minute with varying sizes with another requirement being guaranteed delivery and no out of order messages.