Difference between revisions of "SOAP"

From PeformIQ Upgrade
Jump to navigation Jump to search
Line 8: Line 8:


There are several different types of messaging patterns in SOAP, but by far the most common is the [[Remote Procedure Call]] (RPC) pattern, in which one network node (the client) sends a request message to another node (the server), and the server immediately sends a response message to the client. SOAP is the successor of [[XML]]-RPC, though it borrows its transport and interaction neutrality and the envelope/header/body from elsewhere, probably from WDDX
There are several different types of messaging patterns in SOAP, but by far the most common is the [[Remote Procedure Call]] (RPC) pattern, in which one network node (the client) sends a request message to another node (the server), and the server immediately sends a response message to the client. SOAP is the successor of [[XML]]-RPC, though it borrows its transport and interaction neutrality and the envelope/header/body from elsewhere, probably from WDDX


== Related Links ==
== Related Links ==
Line 19: Line 18:
* [http://xml.apache.org/ Apache XML implementation]
* [http://xml.apache.org/ Apache XML implementation]
* [[SOAP Tools and Implementations]]
* [[SOAP Tools and Implementations]]


== Python Tools ==
== Python Tools ==


== Also ==
== Also ==

Revision as of 13:19, 25 January 2008

Full Name

Simple Object Access Protocol - SOAP

Information

SOAP (see below for name and origins) is a protocol for exchanging XML-based messages over computer networks, normally using HTTP/HTTPS. SOAP forms the foundation layer of the Web services stack, providing a basic messaging framework that more abstract layers can build on.

There are several different types of messaging patterns in SOAP, but by far the most common is the Remote Procedure Call (RPC) pattern, in which one network node (the client) sends a request message to another node (the server), and the server immediately sends a response message to the client. SOAP is the successor of XML-RPC, though it borrows its transport and interaction neutrality and the envelope/header/body from elsewhere, probably from WDDX

Related Links

Python Tools

Also