1 / 10

Simple Object Access Protocol (SOAP )

Simple Object Access Protocol (SOAP ). Mark H Needleman Data Research Associates, Inc. ZIG Meeting December 2000. Background. Developed by IBM, Microsoft, Lotus, and others Submitted to W3C - Became W3C Note in May 1998 Current Version is 1.1 See: http://www.w3.org/TR/SOAP

dalmar
Download Presentation

Simple Object Access Protocol (SOAP )

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Simple Object Access Protocol(SOAP) Mark H Needleman Data Research Associates, Inc. ZIG Meeting December 2000

  2. Background • Developed by IBM, Microsoft, Lotus, and others • Submitted to W3C - Became W3C Note in May 1998 • Current Version is 1.1 See: • http://www.w3.org/TR/SOAP • Input Document to New W3C XML Protocol Working Group

  3. Design Goals • Simplicity • Extensibility • Not Exclusive to HTTP - HTTP Binding defined in Specification • Need to expose more of what is being run on top of HTTP to help Fireall Administrators do better filtering

  4. SOAP Design • Lightweight Information Exchange in a Decentralized Environment • XML Based • Envelope/Body Framework for defining whats in a message and how to process it • Encoding Rules • Convention for expressing RPC calls and responses

  5. Sample Soap Message POST /StockQuote HTTP/1.1Host: www.stockquoteserver.comContent-Type: text/xml; charset="utf-8"Content-Length: nnnnSOAPAction: "Some-URI"<SOAP-ENV:Envelopexmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><SOAP-ENV:Body><m:GetLastTradePrice xmlns:m="Some-URI"><symbol>DIS</symbol></m:GetLastTradePrice></SOAP-ENV:Body></SOAP-ENV:Envelope>

  6. SOAP Message Embedded in HTTP Response HTTP/1.1 200 OKContent-Type: text/xml; charset="utf-8"Content-Length: nnnn<SOAP-ENV:Envelopexmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/><SOAP-ENV:Body><m:GetLastTradePriceResponse xmlns:m="Some-URI"><Price>34.5</Price></m:GetLastTradePriceResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>

  7. SOAP Messaging Models • Request/Response • One way • Multicast

  8. Why NCIP Did Not Use SOAP • Not an “Official Standard” • Uncertainty about support • Lack of Deployment • Some Ignorance about SOAP Itself • Didn’t want to add one more level of complexity into the mix • No good sense of what it would do for us or what problems it might solve

  9. W3C XML Protocol WG • Developing an Envelope for encapsulating XML - must support distributed extensibility, evolvability, and intermediaries • A convention for the content of the envelope when used for RPC • A mechanism for serializing data • A convention for the use of HTTP

  10. XML Protocol WG (2) • Currently defining requirements - expect to publish initial draft soon • Will be coordinating with other activities like IETF work • Doing much of its work publicly - discussions happen on public mailing list • xml-dist-app@w3.org

More Related