PowerPoint Presentation

SOAP communication styles:SOAP supports two possible communication styles:Remote procedure call (RPC)Document (or message).1Remote Procedure Call (RPC)-Style:

SOAP-RPC is an implementation of a Remote Procedure Call (RPC). A function on a remote machine is called as if it were a local function. All of the marshaling and unmarshaling of data is handled by SOAP and is performed in XML. RPC-style web services are tightly coupled and interface-driven. The clients invoke the web service by sending parameters and receiving return values.

RPC(cont..)RPC-style web services follow call/response semantics; therefore, they are usually synchronous, which means that the client sends the request and waits for the response until the request is processed completely.

RPC:

Document-style:With a document style message the client and/or server passes an XML document as the body of the SOAP message instead of parameters. An example of this is an invoice. The document is marked-up with both XML and a schema, which is common to both the sender and receiver.The sender is the consumer, which makes a function call to the web service with some parameters, and in return the vendor sends back, not data results, but an XML document that contains all of the information that a normal invoice would have.Document-style(cont)Since a document message is usually a self-contained XML le, it is better suited for asynchronous processing and can be placed directly into the queue.Document-style