- From: David Orchard <dorchard@bea.com>
- Date: Wed, 5 Jul 2006 15:26:42 -0700
- To: <larssont@student.chalmers.se>, <www-ws@w3.org>
Hi Johan, BEA Systems has authored the SOAP-Conversation specification [1] which is RF and implemented in Weblogic 8 and 9. We are updating to the latest versions of WS-Addressing and refactoring into WS-Conversation and WS-Callback, an early version at [2]. This is a lightweight protocol that just does a conversation id with optional and composable conversation callback. It isn't a member submission, but certainly could easily be. We are certainly friendly to the W3C Patent Policy terms in this area. Let me know if I can be of further help. Cheers, Dave [1] http://dev2dev.bea.com/pub/a/2002/06/SOAPConversation.html [2] http://dev2dev.bea.com/webservices/WS-CallBack-0_9.html > -----Original Message----- > From: www-ws-request@w3.org [mailto:www-ws-request@w3.org] On Behalf Of > Johan Tibell > Sent: Wednesday, July 05, 2006 2:18 AM > To: www-ws@w3.org > Subject: W3C standard for (stateful) SOAP conversations? > > > Hi, > > I'm looking for a SOAP extension that could fulfill the following use > case: > > Airlines want to allow customers to book flights online. This is a > multi-step process and some information needs to be stored on the server > during the process. Basically I want a conversation id (or something > similar) associated with several messages so that the server can associate > this id with some information kept locally. > > Is this already addressed by some current protocol specification? > > Note: I'm rather limited in my selection of protocols (because of > political reasons), more specifically I can't go with a solution that is > completely stateless and thus imbeds state information, ala cookies, in > the messages themselves. Of course if you know of such a solution you > could still point it out as it would be interesting to me even if I can't > use it. > > Best regards, > > Johan Tibell > >
Received on Wednesday, 5 July 2006 23:03:35 UTC