WCF will do the REST of it for you...

So, in the interests of interop, we're going to be exposing all of our SOAP/WS-* services RESTfully too. Okay, I'm there conceptually, but I have some serious concerns about logistics.

So, I thought I'd detail what it takes to go from a "Microsoftie-thats-perfectly-happy-with-SOAP-because-Visual-Studio-does-all-the-hard-work-for-me" type to a "hey-lookee-lookee-I'm-interoperable-because-I've-been-freed-from-the-strictures-of-WS-*" type.

Note that this is, for some reason, a highly charged topic to discuss. While I'm sure I have enough say that I could put the kibosh on the whole thing, something tells me that there must be something to this or I wouldn't have a good 50% of developers jumping out of the woodwork yelling "POST is evil!!!!1111!!1" ;-)

See? http://cafe.elharo.com/web/rest-vs-soap-a-parable/

So, I'm curious on which side I will fall.

Let's see...