title: What can WCF WebHttp do that ASP.NET MVC cannot?
body: <p>Please, no "They solve 2 different problems" answers, it's the same <strong>HTTP request and response</strong> problem. Just because you have views/templates in MVC doesn't mean you have to use them. M_C is good enough for serving XML and JSON.</p>
  
  <p>Please, no "It's what Microsoft says you should do" answers. If I thought that way I wouldn't be asking this question.
  <hr/>
  Apparently people did not like how I phrased my question, but the title is very clear. I'd like to learn what WebHttp can do that MVC can't, or what both can do but with WebHttp it's easier or more powerful.
  <hr/>
  I'm really looking for details, not a high level description of when to choose one over the other.</p>