andrew222
December 19th, 2010, 08:24 PM
Hello,
I have been reading up on the differences between SOAP and REST.
I am getting the impression that SOAP would be used for a service that would invoke behavior, provide a contract and address interoperability through the use of XML.
I am also getting the impression that REST is good for managing information with create, read, update and delete statements. An individual resource can be indexed via a URL which can address security and caching much easier than a WSDL based SOAP Web Service.
I am curious if there is anyone out there who has had to create a Web Service and split it into to two Web Services; one SOAP WS for invoking behavior and a separate REST WS for simply reading and updating a resource.
I have been reading up on the differences between SOAP and REST.
I am getting the impression that SOAP would be used for a service that would invoke behavior, provide a contract and address interoperability through the use of XML.
I am also getting the impression that REST is good for managing information with create, read, update and delete statements. An individual resource can be indexed via a URL which can address security and caching much easier than a WSDL based SOAP Web Service.
I am curious if there is anyone out there who has had to create a Web Service and split it into to two Web Services; one SOAP WS for invoking behavior and a separate REST WS for simply reading and updating a resource.