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


From: Marc Hadley <marc.hadley@sun.com>
Date: Tue, 29 Jan 2002 17:54:37 +0000
Message-ID: <3C56E1DD.50709@sun.com>
To: XML Protocol Discussion <xml-dist-app@w3.org>
Following on from our discussion on the TBTF call today I would like to 
raise a point that I alluded to in a previous message [1]. I think that 
current text does not draw enough distinction between SOAP message 
exchange patterns and transport message exchange patterns and as a 
result is rather confusing.

In order to address the confusion I would propose that when we refer to 
MEPs in the specification we refer to SOAP MEPs, i.e. patterns of 
exchange of SOAP messages rather than underlying protocol exchanges. We 
would define an open ended set of such MEPs: outbound one-way, inbound 
one-way, request-response, ... The purpose of a binding specification 
would be to describe how an underlying protocol is used to support a set 
of these SOAP MEPs plus any other features desired. Our HTTP binding 
specification would describe how HTTP is used to provided the SOAP MEPs 
that we decide we want to support.

We also need to decide a number of issues including:

(i) Can a SOAP MEP be split over multiple bindings ? E.g. request 
response with request via HTTP, response via SMTP.
(ii) Are SOAP MEPs single hop or multi-hop in nature ?

and what bearing the answers to these questions have on bindings 
"supporting" a given MEP.


[1] http://lists.w3.org/Archives/Public/xml-dist-app/2002Jan/0194.html
Received on Tuesday, 29 January 2002 12:54:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:18 UTC