This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: A Pox on your REST! A Pox, I say!
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.
After reading Clemens' "Teaching Indigo to do REST/POX" I, a MEST-er, am compelled to retort. Of course, this has nothing to do with Indigo, or Clemens, who I highly respect. Just that I think the whole REST thing needs to be put to rest. This will doubtless stir the fires of the REST/MEST war again, so I'll keep to my point - or rather, just raise a question:
A non idempotent message: Withdraw $100 Billion. Easily mapped to REST.
An idempotent message: If transaction #X has not been processed, withdraw $100 Billion as transaction #X. How do you express that REST-fully?
In my opinion, MEST enables idempotency better than REST by simply removing the limitations that the REST verbs put in place.