W3C home > Mailing lists > Public > xml-dist-app@w3.org > February 2002

RE: Issue 133: SOAP and Web Architecture: Draft sentences for HTTP bi nding preamble.

From: Henrik Frystyk Nielsen <henrikn@microsoft.com>
Date: Mon, 18 Feb 2002 14:52:53 -0800
Message-ID: <79107D208BA38C45A4E45F62673A434D067C7FF7@red-msg-07.redmond.corp.microsoft.com>
To: "Williams, Stuart" <skw@hplb.hpl.hp.com>, <xml-dist-app@w3.org>

Fine with me, thanks!

Henrik Frystyk Nielsen
mailto:henrikn@microsoft.com

>-----Original Message-----
>From: Williams, Stuart [mailto:skw@hplb.hpl.hp.com] 
>Sent: Monday, February 18, 2002 04:24
>To: 'xml-dist-app@w3.org'
>Subject: Issue 133: SOAP and Web Architecture: Draft sentences 
>for HTTP bi nding preamble.
>
>
>As part of the resolution of Issue 133: SOAP and Web 
>Architecture [1], I was actioned to draft text for inclusion 
>in the SOAP 1.2 spec. to address the resolution of Issue 133. 
>Issue 133 was closed during the WG telcon on 13th Feb with 
>resolution reported to xmlp-comments@w3.org in [2].
>
>Proposed draft text for insertion into SOAP 1.2 Part 2 Section 
>7 [3] follows
>below:
>
><draft>
>7 Default HTTP Binding
>
><insertion>
>The SOAP Binding Framework enables the definition of multiple 
>bindings between SOAP and a given underlying protocol. The 
>HTTP binding specified in the following subsections makes use 
>of the HTTP POST method to transfer SOAP messages between SOAP 
>Nodes. Note that nothing precludes the specification of 
>different HTTP bindings that make use of other HTTP methods, 
>or indeed that make different use of the HTTP POST method. It 
>is also possible to use the HTTP binding specified here in a 
>way that preserves the semantics of the HTTP POST method [ref 
>RFC2616], however the onus to ensure the preservation of HTTP 
>POST semantics falls upon the SOAP application developer. </insertion>
>
>7.1 Introduction
>
>This SOAP binding specification adheres to the SOAP Binding 
>Framework (see SOAP Transport Binding Framework), and as such 
>uses abstract properties as a descriptive tool for defining 
>the functionality of certain features. </draft>
>
>Comments? Flames? etc.
>
>Best regards
>
>Stuart Williams
>[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x133
>[2] http://lists.w3.org/Archives/Public/xmlp-comments/2002Feb/0011.html
>[3] 
>http://www.w3.org/2000/xp/Group/1/10/11/soap12->part2.html#soapinhttp
>
>
>
Received on Monday, 18 February 2002 17:53:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:06 GMT