- From: Jacek Kopecky <jacek@systinet.com>
- Date: Wed, 22 May 2002 17:53:26 +0200 (CEST)
- To: Prasad Yendluri <pyendluri@webMethods.com>
- cc: www-ws-desc@w3.org
Prasad,
I don't believe this is needed. An other name of one-way
messages is fire-and-forget. This feature is seldom suitable, but
sometimes you just don't need to know. 8-)
If we added the possibility of a fault, we would be adding the
response at the same time, if only because no response ==
success response.
IMHO one-way operations are exactly that, with the possibility
of finding out the result or failure by other means, if the
application requires it.
My proposal is to resolve this issue by saying "the current way
is how we want it."
Jacek Kopecky
Senior Architect, Systinet (formerly Idoox)
http://www.systinet.com/
On Tue, 21 May 2002, Prasad Yendluri wrote:
> Currently the One-Way operations do not provide for returning faults.
> That is, they only have a input message but no fault. Does that mean a
> one-way operation must always succeed? What if the the request is bad or
> somehow can not be processed and/or meets one of the SOAP-Fault
> conditions (assuming SOAP binding)?
>
> It seems desirable to permit faults with One-Way operations?
>
> Comments?
>
> Regards, Prasad
>
>
>
Received on Wednesday, 22 May 2002 11:53:28 UTC