RE: Web Services Description Conference call minutes for April 18 , 20 02

>So I'm ok with tieing the removal of S-R and O-O operations to a solution
>to case 1, but yet not tieing that to adding an event mechanism. What that
>amounts to saying is that I could live with WSDL 1.2 having a better way
>to support case (1), but possibly not having an event mechanism until
later.

+1



-----Original Message-----
From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
Sent: Wednesday, April 24, 2002 4:49 AM
To: www-ws-desc@w3.org
Subject: Re: Web Services Description Conference call minutes for April
18 , 20 02


I agree WSDL needs to have the ability to define events. It is useful
to note though that WSDL 1.1 does not support events right now.

Both solicit-response (S-R) and output-pnly (O-O) style operations are
currently unusable in WSDL 1.1 as there are no bindings defined for
them. What I'm proposing is that we find better ways to do what those
were intended to cover (which was mostly what Prasad writes as case 1
below).

So I'm ok with tieing the removal of S-R and O-O operations to a solution
to case 1, but yet not tieing that to adding an event mechanism. What that
amounts to saying is that I could live with WSDL 1.2 having a better way
to support case (1), but possibly not having an event mechanism until later.

I'm separating the solutions to the two cases as I see them being quite
different. The case (1) solution can be something along the lines of what
I posted earlier today, whereas the case (2) solution is a bit more
complex because of the need for a subscription mechanism and passing of
service references etc..

Igor, is that ok with you?

Sanjiva.

Received on Wednesday, 24 April 2002 15:52:24 UTC