On Sun, 2006-11-26 at 19:49 +0100, Stefan Tilkov wrote: > > 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 :-)
So if I may extrapolate a bit .. are you seriously saying that the Web as it existed in 1996 (HTTP, URIs, XML, REST) is *all* that is needed to replace EDI, MQ and all the bazillion integration technologies and the only reason it hasn't been used for that for the last 10 years is simply lack of understanding? Do you seriously mean to say that we've had the silver bullet in our hands all these years and simply didn't know it?? No, you can't be serious :). To me, Web services is building on the Web to create a set of standards that are needed to make integration ubiquitous, just as much as the Web has made information dissemination ubiquitous. I clearly don't believe the 1996 Web is enough. Sanjiva. -- Sanjiva Weerawarana, Ph.D. Founder & Director; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Director; Open Source Initiative; http://www.opensource.org/ Member; Apache Software Foundation; http://www.apache.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
