SOAP is Dead?
Mmm…may be a little premature to make that call, but it’s good to see the alternatives getting a run. Following on from my last post, here are some more links:
Nelson Minar tells us Why SOAP Sucks, based on his experience helping Google implement SOAP APIs.
Duncan Cragg’s is writing a 9 part series titled “The REST Dialogues”:
Part 1: Getting Data.
Part 2: Setting Data.
I really think that the whole SOAP mess is a result of having tool vendors on the standards boards- no interest in simplicity, and a lack of concern for the practical sorts of problems that occur when you want to make small changes...
matt m — 21 November 2006, 01:06
The strong typing issue is familiar. One example was a date value that was passed as a string type because the developers couldn't work out how to get two Microsoft SOAP toolkits to understand it.
My interest is putting the simplicity back in the applications, and making them easy to change over time. I'm sure dynamic languages have role in this. Platforms like NetKernel take this one step further by treating code as just another cached resource. i.e. Even strongly typed Java code is automatically recompiled after a change.
Other than that, only validate the parts of the XML document that you need and ignore the rest. :-)
Andrew
Andrew Hallam — 21 November 2006, 06:59