This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: Don't Mest with Clemens when it comes to REST
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
In response to Clemens' comment on my recent post I'd like to continue asking questions (how else will I learn?):
Clemens:
You could very well POST a new subordinate accounting record for x Euros into an account identified by a URL.
Udi:
Don't the REST purists themselves consider POST something out of the true spirit of Resource Transfer? In the example above, would they not prefer a PUT? In which case, does it not become a conditional PUT?
Finally, I concur with Clemens that both REST and MEST have their sweet spots. However, I believe that there are certain problems that are significantly more difficult to solve in one style than in the other. More so, I believe that these problems are not preference or productivity related, and may be project threatening in the best case, life threating in the worst. In the domain of mission critical systems, I believe that MEST solves more of the difficult problems than REST.