[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [bt-spec] Messaging issues
This synchronous request/response model works well with web services. I think that support for this model is necessary for BTP to succeed. This specific use needs to be described and captured in a profile. For the binding alternatives proposed by Pal 2 and 3 are redundant and 3 should not be supported. Support for both 2 and 3 will only confuse people > Alternative 1: > > sender --> HTTP req + SOAP + BTP "req" --> receiver > sender <-- HTTP res + SOAP + BTP "res" <-- receiver > > Alternative 2: > > sender --> HTTP req + SOAP + BTP "req" --> receiver > sender <-- HTTP res + SOAP (empty) <-- receiver > > sender <-- HTTP req + SOAP + BTP "res" <-- receiver > sender --> HTTP res + SOAP (empty) --> receiver > > Alternative 3: > > sender --> HTTP req + SOAP + BTP "req" --> receiver > sender <-- HTTP res 200 <-- receiver > > sender <-- HTTP req + SOAP + BTP "res" <-- receiver > sender --> HTTP res 200 --> receiver Alastair has brought up some important points on what this means for the coordinator relationships (inability to perform failure recovery between superior and inferior coordinators was specific example provided). The need to support the request/response paradigm has come up several times at meetings. If we need to support it, and I believe that we do, we will first need to quantify the impact on the current spec and publication schedule then look at how to address it. =bill -----Original Message----- From: WEBBER,JIM (HP-UnitedKingdom,ex1) [mailto:jim_webber@hp.com] Sent: Wednesday, October 24, 2001 10:33 AM To: alex@ceponkus.org; bt-spec@lists.oasis-open.org Subject: RE: [bt-spec] Messaging issues Alex, Having being playing with HP's SOAP server amongst others I have come to a similar conclusion. I would like to see SOAP RPC bindings whereby (for example) a BTP begin message (a HTTP request) is met by a BTP begun message (HTTP response). Another use of this is where a factory is asked to create an atom (for which there is no response message(?)) and the SOAP stack can then tag on the appropriate context in the SOAP header onto the HTTP response. Does this sound reasonable? Jim -- Dr. James Webber Hewlett-Packard Arjuna Lab http://www.arjuna.com ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC