Abstract
This chapter discusses the role of Simple Object Access Protocol (SOAP) in Web services and how service nodes process SOAP messages. SOAP is the basic messaging protocol for Web services, other specifications build on top of the SOAP specification or have “bindings” to it. To understand the value of an XML-based protocol for information exchange, it is necessary to understand the doors it has opened. The fundamental shift in distributed computing SOAP has introduced is the ability to communicate between distributed systems that rely on heterogeneous software and hardware stacks. SOAP does not define an object model or language bindings. It provides only the overall framework for an Extensible Markup Language (XML) message to be communicated between a sender and a receiver, genetically called SOAP processing nodes. A node may be a sender, a receiver, or both. This one-way message between nodes is combined to implement request-response, asynchronous messaging, and notification type interactions. An enterprise-level application requires more sophisticated features that offered by SOAP alone.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
