- From: Doug Davis <dug@us.ibm.com>
- Date: Wed, 12 Sep 2001 09:44:47 -0700
- To: paulclinger@yahoo.com
- Cc: xmlp-comments@w3.org
Paul,
This is to notify you that the Working Group has decided to close
issue 93[1] that you reported[2], whose title is "mU at client".
It is believed that the processing model clearly states what the
client should do - it must process the incoming message (from the
server) according to the SOAP processing model - which will include
noticing and correctly processing MU headers. If there is an error
then a Fault MUST be generated - the spec is, for the most part,
silent on what happens with the Fault since that will be a choice
based on the application semantics and the Transport Binding. The
spec does talk about it in specific cases, like the server side of
RPC [2], but you asked about the client side. 8-)
Let us know if this is an acceptable resolution.
-Dug
[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x93
[2] http://groups.yahoo.com/group/soapbuilders/message/2017
[3] http://www.w3.org/2000/xp/Group/1/06/01/xmlp-soap-02.html#_Toc478383532
Paul Kulchenko <paulclinger@yahoo.com> on 04/18/2001 09:07:23 AM
Please respond to soapbuilders@yahoogroups.com
To: soapbuilders@yahoogroups.com
cc:
Subject: [soapbuilders] mustUnderstand on client side
Hi, All!
Since it's possible to return Header from server to client also, what
should client do if this header has mustUnderstand attribute or wrong
actor?
Best wishes, Paul.
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
Yahoo! Groups Sponsor
Click Here!
[IMAGE]
To unsubscribe from this group, send an email to:
soapbuilders-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Received on Wednesday, 12 September 2001 12:45:19 UTC