Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Nov 07, 2012 01:57 AM by marvindev
Nov 06, 2012 05:04 AM|LINK
Hi, I need to evaluate the ASP.NET MVC WEB API to see if we can adapt this framework for one of RESTFul web service we want to write. We started initial proptotyping using raw HTTP Handlers and Modules. But like to understand pros and cons of WEB API.
What are key pros and cons for WEB API againts declaring routes in a “traditional” way.
Nov 06, 2012 09:26 AM|LINK
here, the list of features you get with Web API that you don't get with HTTP Handlers and Modules (unless you code it) is:
Nov 06, 2012 12:47 PM|LINK
As Darrell said, there are a lot of very useful features in WebAPI that you'd not want to have to write on your own. I can't imagine doing all of this in raw http handlers.
Nov 06, 2012 05:13 PM|LINK
I strong prefer use ASP.NET WebAPI. Only cons I know is there will some learning curve. If you have some idea about MVC Architectue style it is very easy. If you don't have MVC background that's not a problem you can still learn Web API Quickly.
Pros:- There are lot of pros it's hard to explain in few lines. Please see this vedio.
Nov 07, 2012 01:57 AM|LINK
Thanks Darrell and others for putting it clearly. We are working on PoC with Web API to test if it fits our needs. The only confusion came up due to some of the URLs needed custom routers and as suggested by you in prev post we will explore
AttributeRouting library along with WEB API for the same.