W3C home > Mailing lists > Public > www-ws-desc@w3.org > January 2003

Re: Input-Only Operation

From: Pae Choi <paechoi@earthlink.net>
Date: Wed, 22 Jan 2003 01:06:24 -0500
Message-ID: <002201c2c1dc$9fadf960$0b01a8c0@dev1>
To: "WS Description WG" <www-ws-desc@w3.org>

That makes sense. Thank you.


Pae


> Pae, this operation type (input-only) is for applications where
> subsequent information is not necessary (when the client doesn't care
> whether there has been a failure on the receiving side) or where
> subsequent information is being sent by different means, for example in
> a different operation. In scenarios where a request/response model is
> necessary, it's natural that input/output operations should be used.
>
> Hope I've clarified it,
>
>                    Jacek Kopecky
>
>                    Senior Architect, Systinet Corporation
>                    http://www.systinet.com/
>
>
>
>
>
> On Sat, 2003-01-18 at 15:20, Pae Choi wrote:
> > Under the section, "2.3 PortType Description Component", in the
> > [1] WSDL v1.2 it stated as follows:
> >
> > "Input-Only Operations: Operations which have only an input message. The
> > semantics are that when a message is sent to the service, the service
> > consumes it but does not produce any output message. There MUST NOT be
any
> > fault messages indicated in this case."
> >
> > Say a client sends a message with the "Input-Only Operation"
> > mode to a service. And there is a failure during the process at
> > the service site and the service is not returning the "fault"
> > message(s) according to the statement in the [1], how can the
> > client make decisions without having the fault message(s) from
> > service for the follow-up actions.
> >
> > Any comments and/or pointers will be apprecated.
> >
> >
> > Pae
> >
> >
> >
> > [1] http://www.w3.org/TR/wsdl12
> >
>
Received on Wednesday, 22 January 2003 01:07:27 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:22 GMT