SOAP Protocol Application

Let's take a look at the content of the SOAP protocol and understand that this Simple Object Access Protocol plays an important role in some important applications. Here we mainly analyze RPC and SOAP protocol applications.

SOAP-RPC

In essence, a SOAP message is a one-way transmission from the sender to the receiver, but it is often combined into a real-time request/response mechanism. To enable RPC to use SOAP, several rules must be followed. First, the request and response messages must be encoded into the structure type. Each input parameter of an operation must have an element of the same name or a member of the input structure. Each output parameter must have a name matching element or a member of the output structure ).

Based on RPC, some SOAP messages displayed earlier are omitted. The following table lists the SOAP request and response packages that only contain packets:

The GetLastTradePrice method must be called in the request DEF response 22.50 request. Note that the response defines the GetLastTradePriceResponse operation. A common SOAP call rule that attaches a response to the end of a response operation is to create a response structure. This output structure contains an element named price. It returns the result of a method call, which is assumed to be a floating point.

There is no explicit declaration of the Data Type in the SOAP envelope. It is important to note that, if you only view the SOAP message, you will not know the symbol type or the price of the result parameter). Client applications generally define data types through Section 5 encoding, or through private agreements with the server. In either case, the definitions contained in the SOAP message are not explicit.

Finally, a low-level protocol such as HTTP is required for RPC. Although the SOAP1.0 specification requires the use of HTTP as the transmission protocol, the SOAP1.1 specification and its sister specification "SOAP messages with attachments") allow the use of FTP, SMTP, and even possible) the original TCP/IP socket. All these general serialization and encoding rules for SOAP are also applicable to RPC parameters.

SOAP Protocol Application

Client Applications in some places on the Internet use Web services.

The Web service displays the object method through SOAP.

Object method to access remote data anywhere on the Web.

For the transfer logic of these network proposition applications, we can draw a general conclusion for Web Services and the SOAP protocol:

Clients at some locations can enable data at any location on the Web. This is what we want to prove.

The following is a more detailed example.

The SOAP client uses UDDI registration to find Web Services. You do not need to directly operate the WSDL. In most cases, the SOAP application will be hard-connected to the binding of a specific type of port and a specific style, in addition, it dynamically configures the service address to be called through UDDI that matches the discovered Web service. The client application creates a SOAP message, which is an XML document that can execute the desired request/response operations. The client sends the SOAP message to the JSP or ASP page on the Web server listening for the SOAP request. The SOAP server parses the SOAP package and calls appropriate object methods in its field, and transmits the parameters contained in the SOAP document. Before the SOAP server receives a message, the intermediate processing node can execute the special function indicated by the SOAP header to determine whether to perform this step as needed. The request object executes the directive function and returns data to the SOAP server. It packs the response to the SOAP envelope. The server wraps the SOAP envelope in the response object to be sent back to the requesting machine, such as a servlet or COM object. The client receives the object, removes the SOAP envelope, and sends the response document to the process of the initial request to complete the request/response loop.

Summary

The SOAP protocol is an XML-based protocol used to send messages in a distributed environment and execute remote calls. With SOAP, data serialization is possible without considering any specific transmission protocol, although HTTP is usually used. Using SOAP to build a platform and a language-neutral interoperability system is a good choice. In short, SOAP and Web services have taken everything into consideration to build a distributed application infrastructure on XML. By resolving conflicts between the COM and Java component object models, SOAP minimizes the incompatibility issues that occur when multiple platforms access data. Put these discussions aside, SOAP is an ideal medium for all types of object entities, even for Hollywood movie roles like Brad Pitt and Edward Norton. Just like in movies, we look forward to the effects of this new technology on the world.