SOAP - Wiki
SOAP - Wiki
1 of 5
https://en.wikipedia.org/wiki/SOAP
SOAP (Simple Object Access Protocol) is a protocol specification for exchanging structured information in
the implementation of web services in computer networks. It uses XML Information Set for its message format,
and relies on application layer protocols, most often Hypertext Transfer Protocol (HTTP) or Simple Mail
Transfer Protocol (SMTP), for message negotiation and transmission.
SOAP provides the Messaging Protocol layer of a web services protocol stack for web services. It is
XML-based protocol consisting of three parts:
an envelope, which defines the message structure[1] and how to process it
a set of encoding rules for expressing instances of application-defined datatypes
a convention for representing procedure calls and responses
SOAP has three major characteristics:
1. extensibility (security and WS-routing are among the extensions under development)
2. neutrality (SOAP can operate over any transport protocol such as HTTP, SMTP, TCP, UDP, or JMS)
3. independence (SOAP allows for any programming model)
As an example of what SOAP procedures can do, an application can send a SOAP request to a server that has
web services enabledsuch as a real-estate price databasewith the parameters for a search. The server then
returns a SOAP response (an XML-formatted document with the resulting data), e.g., prices, location, features.
Since the generated data comes in a standardized machine-parsable format, the requesting application can then
integrate it directly.
The SOAP architecture consists of several layers of specifications for:
message format
Message Exchange Patterns (MEP)
underlying transport protocol bindings
message processing models
protocol extensibility
SOAP evolved as a successor of XML-RPC, though it borrows its transport and interaction neutrality and the
envelope/header/body from elsewhere (probably from WDDX).
SOAP was designed as an object-access protocol in 1998 by Dave Winer, Don Box, Bob Atkinson, and Mohsen
Al-Ghosein for Microsoft, where Atkinson and Al-Ghosein were working.[2] Due to politics within
Microsoft,[3] the specification was not made available until it was submitted to IETF 13 September 1999.[4][5]
Because of Microsoft's hesitation, Dave Winer shipped XML-RPC in 1998.[6]
The submitted Internet Draft did not reach RFC status and is therefore not considered a "standard" as such.
8/3/2016 12:08 PM