Re: Solicit Response And Notification in WSDL 1.1

Hi Naresh,

I think the thinking behind the "solicit-response", RPC transmission
primitive, is that the two end-points are conducting a conversation within
some type of session :-)

There are a couple ways that one could interpret this:

1. The end-point that started the conversation, receives a request from the
end-point that it sent it's request, before it receives a response to it. In
essence, the originating end-point (we'll call it end-point X) starts out
being a "service consumer", intermediately becomes a "service provider", and
then switches back to being a "service consumer" :-) The
"client-server-challenge" sequence in SSL and Kerberos, are good "real
world" examples of this type of exchange protocol.

2. An end-point that usually assumes the role of "service provider",
intermittantly becomes a "service consumer". Agents do this type of thing
with centralized Agent Managers.

In both cases, I think the WSDL "solicit-response" mechanism only covers the
original "service provider" (we'll call this end-point Y) making a request
of the original "service consumer" (what we already called end-point X). So
in the following WSDL extract:

<portType name="GoNoGoForLaunchPortType" >
   <operation name="GoNoGoForLaunch">
      <output message="tns:GoNoGoForLaunchSolicitation"/>
      <input message="tns:GoNoGoForLaunchResponse"/>
   </operation>
</portType>

Here, end-point X (the original "service consumer") would implement the
"GoNoGoForLaunchPortType" port type. Same with the "notification" UDP-style
transmission primitive :-)

Regards,
Mike Wooten

>From: Naresh Agarwal <[email protected]>
>Reply-To: Discussion of implementing SOAP applications today
><[email protected]>
>To: [email protected]
>Subject: [SOAP] Solicit Response And Notification in WSDL 1.1
>Date: Tue, 30 Jul 2002 22:53:13 +0530
>
>         Hi,
>WSDL has four transmission primitives  (Section 2.4, WSDL 1.1 ) that an
>endpoint (say X) can support-
>*       One-way. The endpoint X receives a message.
>*       Request-response. The endpoint X  receives a message, and sends a
>correlated message.
>*       Solicit-response. The endpoint X sends a message, and receives a
>correlated message.
>*       Notification. The endpoint X sends a message.
>
>
>In case of Solicit-response, WSDL for endpoint X, would look like as
>follows:
>
><wsdl:definitions .... >
>     <wsdl:portType .... > *
>         <wsdl:operation name="A" parameterOrder="nmtokens">
>            <wsdl:output name="nmtoken"? message="qname"/>
>            <wsdl:input name="nmtoken"? message="qname"/>
>            <wsdl:fault name="nmtoken" message="qname"/>*
>         </wsdl:operation>
>     </wsdl:portType >
></wsdl:definitions>
>
>In case of Notification, WSDL for endpoint X, would look like as follows:.
>
><wsdl:definitions .... >
>     <wsdl:portType .... > *
>         <wsdl:operation name="B">
>            <wsdl:output name="nmtoken"? message="qname"/>
>         </wsdl:operation>
>     </wsdl:portType >
></wsdl:definitions>
>
>
>Now an endpoint (say Y ), needs to communicate with X using it's WSDL.
>
>In case of Solicit-Response and Notification, the endpoint X would send
>some message to endpoint Y.
>
>Now, I have following queries:-
>
>1) Who has (X or Y) implemented the operations A and B?
>2) Who would call (X or Y) the operations A and B?
>
>Any help would be greatly appreciated!
>
>thanks,
>regards,
>Naresh Agarwal
>
>You can read messages from the SOAP archive, unsubscribe from SOAP, or
>subscribe to other
>DevelopMentor lists at http://discuss.develop.com.




_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com

You can read messages from the SOAP archive, unsubscribe from SOAP, or subscribe to other
DevelopMentor lists at http://discuss.develop.com.