SOAP (Simple Object Access Protocol) is a standard for exchanging XML-based messages via a computer network or a path to a program that runs on an operating system (OS) to communicate with the program on the same or different OS using HTTP and XML as a mechanism for the exchange of data, then SOAP can communicate with a wide range of applications even though there is a difference in operating systems, technologies, and programming languages. Actually the role of SOAP in web service technology as packaging Protocol for messages (messages) used jointly by users and applications clearly specified how to encode the HTTP headers and XML file so that a program on one computer can call a program on another computer and transmit the information, and how a program called give a response. The SOAP along with its development has two types namely Soap version 1.1 and Soap version 1.2. Discover the difference on the article written here as well as with the conclusion at the end of the paragraph.
By using XML, you can get a simple and lightweight way to do exchanging structured and types information between peers in a decentralized. SOAP version 1.1 consist of 3 parts, we will mention it one by one. The Soap envelope construct defines an overall framework for expressing what is in a message; who should deal with it, and whether it is optional or mandatory. Other one, The SOAP encoding rules defines a serialization mechanism that can be used to exchange instances of application-defined datatypes. And the last one, The SOAP RPC representation defines a convention that can be used to represent remote procedure calls and responses. This SOAP’s purpose “there are several features from traditional messaging systems and distributed object systems that are not part of the core SOAP specification”.
SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. “Part 1: Messaging Framework” defines, using XML technologies, an extensible messaging framework containing a message construct that can be exchanged over a variety of underlying protocols. In SOAP version 1.2, all the current versions of SOAP, also including the old version (1.1). There are two main goals from SOAP 1.2 which are simplicity and extensibility. And there are 3 parts available in SOAP 1.2. First, The SOAP processing model defining the rules for processing a SOAP message. Second, The SOAP Extensibility model defining the concepts of SOAP features and SOAP modules, and the last The SOAP underlying protocol binding framework describing the rules for defining a binding to an underlying protocol that can be used for exchanging SOAP messages between SOAP nodes.
|Soap 1.1||Soap 1.2|
|- Exchanging structured and types information between peers in a decentralized||- Exchanging structured information in a decentralized, distributed environment|
|- Using XML||- Using XML technologies|
|- Consist of 3 different parts||- Containing a message construct|
Soap 1.1 vs 1.2
We can see from SOAP 1.2, there are a lot of things that have changed from the previous SOAP 1.1. There are also a lot of new features in there. The changes to the SOAP 1.2 specification that are significant include the following updates: SOAP 1.1 is based on XML 1.0. SOAP 1.2 is based on XML Information Set (XML Infoset).