I feel, that MVVM and REST being considered together can produce a solid and reliable pattern for programming for many years. (My intuition says me that we SHOULD consider them together). Also it seems that it should be a proper abstraction for Asynchronous operations in ViewModels and Controllers – like a composable asynchronous data dependency graph (with support of transactions) – thing that operates at higher level of abstraction than c# 4.0 parallels (closer to busines logic).
Are there any investigations, or best practices on that?
- MVVM + REST – ?
- MVVM + AsyncModels – ?
- REST + AsyncModels – ?
- MVVM + REST + AsyncModels – ?
I completely agree with you in that MVVM + Rest together are a perfect combination.
Maybe the problem for this to get more interest is that his natural target are Silverlight applications, and the framework they are promoting there is RIA Services.
I personally prefer to get data from a Rest server, and to have my MVVM Model objects correspond to Rest resources.
I don’t know any investigations about this, but sure is an interesting topic. About the async operations i would suggest using couroutines, based in IEnumerable. I know 2 frameworks that use that:
1) caliburn
2) the Dream Rest framework, but (for what i know) is not silverlight.