Yes, SOAP/WSDL interfaces can be defined in a uniform way, and achieve the same network effects. This tends not to happen in practice, but it can.
Secondly, REST doesn't solve the data interpretation problem, which still exists. It does solve two other big problems: universal identification & access methods. Which are huge wins -- you've already agreed on the semantics of your operation And yes, apologies, document-oriented SOAP/WSDL != RPC. Cheers Stu ----- Original Message ---- From: Steve Jones To: [email protected] Sent: Thursday, July 6, 2006 9:49:47 AM Subject: Re: [service-orientated-architecture] RESTful lightbulb But the same could be said of SOAP/WSDL, indeed most of the financially successful ones out there in industry at the moment appear to be using the SOAP/WSDL approach. Apples and oranges though, one is a human centric system where the interpretation is done people people, and the other is system to system where the interpretation has to be defined and agreed. Integrating businesses and systems is not the same as slapping up a web page. SOAP/WSDL != RPC in every case BTW, that is just one of the available styles. ------------------------ Yahoo! Groups Sponsor --------------------~--> Check out the new improvements in Yahoo! Groups email. http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
