|
this article did layout the problem correctly (SOAP being a RPC based technology). the URI-centric approach is the right direction, but I feel that the author get a little off topic on the second half of the article. the real problem is "we can reference a piece of data in a very decouple, yet flexible way. but now what? how do we operate? how do we use it?" the basic theory is "when we find, we want to decouple it, but when we use, we want to integrate it" it is the integration that make SOAP (and other RPC tech) so weak as a web technology because both side must agree on something to use the data. this agreement range from message format, message meaning, API, technology, to work flow.
bottom line: we also need to ground-breaking architecture for web services integration
ben
|