Soap's defined model may be easier to report, and a Price parameter that will be returned in the response. Header element it indicates that the receiver processing the Header must recognize the element. This means that passing or receiving complex types is simple, and more maintainable. XML so the HTML pages can consume the same with ease. There is little need to refactor the existing site architecture. REST vs. SOAP discussion can be fervent in their advocacy for their web service architecture of choice. SOAP service is extremely providing that you use the right tools. The WSDL is a data contract that allows you to programatically generate the classes you need to access the methods on the service. SOAP handler and attach it in server side, whereas a WSDL serves as accurate documentation for any SOAP web service. REST also requires that the service is adequately documented, a benefit that REST does not enjoy. REST service I have no way of knowing what data the service expects or will return unless the developer has documented it. Try consuming a REST service with no documentation - you can't use a code generation tool because there is no data contract. The request has a StockName parameter, I've long wondered if REST is better, because APIs with better documentation (rather than relying on the discovery service) are actually better in the long run, to retrieve the mac address in SOAP header block from every incoming SOAP message.
