Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
May 02, 2012 02:12 PM|LINK
Performance is a key driver with this project. We don't want generate data and transfer through the wire if it's not used.
In this case, I try to create a resource that already exists.
A status code of 409 means
- The resource I am trying to create already exists
- I should use GET, PUT or DELETE to read, modify or delete it.
There is no need for any other detail, and we won't tolerate such overhead.
I am doing an exercise comparing WCF with MVC for REST API . WCF allows me to control my HTTP requests. MVC4 is a model that I find harder and harder fit in REST paradigm, because of all the overhead and the twisted plumbing to manage HTTP requests.
The early documentation about MVC4 Web Api sounds promisisng, and claims to have thinner footprint, but the more I play with it and the more I realize it has a fairly large overhead and foot print compared to WCF.