Web Things, by Mark Baker

Handy-dandy vintage chart from my local monopoly
(link) [del.icio.us/distobj]

It’s good to see Chris coming around to the “SOAP envelope != SOAP message” view of the world;

After we discussed this issue on the call today, it became clear that I may have been mis-reading ‘response message’ for ‘response envelope’.

DaveO and I were discussing our respective positions on this and I believe that we are in agreement that the reference to “other information structures” includes things like the HTTP status code and other goop.

Woot! But I could have sworn I said that 8-)

So, now that that’s out of the way, and the chameleon view of SOAP is finally getting some respect, can we revisit some the previously discussed implications?

Most importantly perhaps, can we revisit the need for parts (read; wsa:To) of WS-Addressing now that we appreciate that HTTP already provides ultimate destination targetting at the application layer?

Tags: soap, http, web.

Yup. “For the vast majority of uses, I’ll argue that WOA is the most interoperable, easiest to implement, and most highly scalable technique for building great, open Web services that anyone can use.”
(link) [del.icio.us/distobj]