What possible benefits can one derive by using only the controller part of MVC in a service oriented architecture pattern. The database access layer, created by LLBLGen Pro, is manipulated without using the MVC 'model'. And, as we've been using DNN as my content management system, We've created modules that make a call via the 'controller' to the service (REST based). My question is - that we could have done this the simpler way! Why use MVC? Is it a common practice to use MVC this way?
Asked
Active
Viewed 72 times
0
-
maybe webapi would be a better fit – Daniel Powell Aug 27 '12 at 05:29
-
@DanielPowell - Elaborate please. – MontyPython Aug 27 '12 at 05:35
-
1webapi doesnt use views, its just a way to create a restful-ish endpoint that will be consumed by others (put simply), its essentially the M and the C from MVC – Daniel Powell Aug 27 '12 at 06:17
-
@DanielPowell - That's precisely what we're doing here. My real question is 'Why not WCF?' – MontyPython Aug 27 '12 at 06:22
-
1@MontyPython WCF is more inclined to create services based on SOAP based protocol – VJAI Aug 27 '12 at 11:44