.net - What can WCF WebHttp do that ASP.NET MVC cannot? -


Please, "they solve 2 different problems" answers, this is HTTP request and response Trouble Just because you have views / templates in MVC does not mean that you have to use them. MNC is great for XML and JSON service.

Please, no, "this Microsoft tells you what you should do" answer if I think that I would not be asking this question like this


apparently people did not like it How I covered my question, but the title is very clear. I would like to know what WebHttp can do that MVC can not do, or both can do it but with WebHttp it's easy or more powerful
I'm really looking for details, on top of each other No higher level details about selecting one.

There is a lot more overhead in an MVC application since you can not serve other services (not SEO-sensitive) While actually doing "URL-rewriting" does not need to be done, or to understand that Google Robots is not necessary, you do not need it - and therefore routing overhead is unnecessary.

The ASP.NET MVC assembly required for the main MVC functionality includes those specific methods, so they can be larger. If your only purpose is to serve JSON / XML then there is no need for extension methods to create text boxes, checkboxes etc.

Unit testing for WCF service will also be an easy task, because you do not need to bother with counterfeit controllers, fake references etc. (The given JSON-response is the only thing you are providing)

Bottom line - It is unnecessary that use ASP.NET MVC for service not only to JSON-data, as long as You do not want to provide the computor with JSON data in any type of GUI.

A short word comes to mind: KISS :)


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -