On Nov 26, 2006, at 2:49 AM, Sanjiva Weerawarana wrote:
It's more than tool support: what matters on the Web is *interoperability*. If I publish a service and it requires reliabilityto work well, I should be able to publish an interoperable protocol thata client from VB to C to Java to Cobol can do. The only way to do that is to have standards that all vendors support.
Ideally, *every* aspect of a service (in the most general sense) should be standardized for maximum interoperability - we agree. In fact, I believe both the designer of REST and WS-* believed in this -- they just put the emphasis on different aspects.
For example, in the WS-* architecture it is commonly believed that transactions is something that should be supported by the infrastructure, and not need to be redone by every application. In REST, a similar example is a fixed interface with standardized methods (e.g. GET for "safe" operations), or a standard scheme for resource identification.
You claim it's wrong to invent a possibly new and different way to do transactions in every application. I claim it's wrong to invent a new and different application interface in each and every application :-)
Stefan -- Stefan Tilkov, http://www.innoq.com/blog/st/
smime.p7s
Description: S/MIME cryptographic signature
