November 15, 2008 00:57 by admin
So far, in this series of posts, we have got to the stage where we can retrieve different representations of a resource and we can delete a resource using either the HTTP verb DELETE or an overloaded POST. In this entry we will allow the client to PUT a resource onto the server.
November 9, 2008 00:10 by admin
In my last post we introduced overloading of POST as a way to allow clients that can’t make PUT or DELETE requests. We handled the overloading within the controller… the ItemPost method looked for a query string parameter “_method” and if it found it, handed off processing to one of the other actions.
At the end of that post I admitted I wasn’t happy with the approach (as much the same code would be needed time and again throughout the web service) and I suggested some alternatives. As promised, I’ve thought about it and in this post I’ll present the solution I chose.
November 7, 2008 01:45 by admin
Our web service has changed over this series of posts until now it supports a more complex resource… but its still a read only web service. In this post we’ll add support for the DELETE HTTP verb. This should be the simplest of the remaining verbs to implement… but it does highlight some more issues to be dealt with.