Reverse SOAP HTTP binding instead? (was: SOAP MIME Type)

John,

My understanding is that your specification create two new MEPs 
(and probably extends the current SOAP HTTP binding).

Another option (probably more natural) would be to reuse the 
existing SOAP Request-Response MEP, and create instead a "Reverse 
SOAP HTTP Binding". This new HTTP binding would implement the 
SOAP Request-Response MEP backwards, i.e. map a SOAP Request to 
an HTTP Response, etc.

Jean-Jacques.

John Kemp wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Rich,
> 
> On Wednesday, May 7, 2003, at 22:09 US/Eastern, Rich Salz wrote:
> 
>>
>>>> BTW, if the SOAP request is the HTTP response, then where's the SOAP
>>>> response go?
>>>
>>>
>>> In the HTTP request, obviously ;)
>>
>>
>> I was serious.  What's the message flow like?
> 
> 
> I was serious too. The binding supports two MEPs - request/response with 
> the initiator making an HTTP request to a (HTTP) server which returns a 
> SOAP Request in an HTTP Response. The initiator then sends a SOAP 
> response in the body of an HTTP request, and the server responds with 
> the appropriate content. A response-only MEP is also supported, in which 
> the initiator sends an HTTP request, to which the HTTP server counters 
> with a SOAP response.
> 
> You can read the whole document at http://www.projectliberty.org/specs - 
> - "Liberty Reverse HTTP Binding", Aarts, R, ed. Liberty Alliance Project 
> (DRAFT), April 2003.
> 
> - - JohnK
> ________________________________
> John Kemp / [email protected]
> (+1) 413.458.9053    /    frumioj@AOL
> Coordinating Editor   /   Project Liberty
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (Darwin)
> 
> iD8DBQE+ukYKn677NT86+ZsRAtfAAKCXe/KWvMg/C2fERpbQBjnBAvurtgCdH+uP
> uijpVHmQHOO9CsjdM8jhg84=
> =bhza
> -----END PGP SIGNATURE-----
>