RE: Problem with "Fault Replaces Message" rule

In order to mitigate denial of service attacks one does not want to
REQUIRE that fault messages be sent at all. SOAP was very careful to say
'generate a fault' rather than 'send a fault message'

Gudge

> -----Original Message-----
> From: www-ws-desc-request@w3.org 
> [mailto:www-ws-desc-request@w3.org] On Behalf Of paul.downey@bt.com
> Sent: 09 October 2003 15:42
> To: dbooth@w3.org; www-ws-desc@w3.org
> Cc: alewis@tibco.com
> Subject: RE: Problem with "Fault Replaces Message" rule
> 
> 
> How about:
> 
>   "The fault message MUST be *sent* to the same target node 
> as the message it replaces." 
> 
> Paul
> 
> 
> -----Original Message-----
> From: David Booth [mailto:dbooth@w3.org]
> Sent: 09 October 2003 07:47
> To: WS Description List
> Cc: Amelia A. Lewis
> Subject: Problem with "Fault Replaces Message" rule
> 
> 
> 
> I think there is a problem with the "Fault Replaces Message" 
> rule[1] in that it *requires* the fault to be sent, which may 
> not always be possible when something has gone wrong.
> 
> 1. http://tinyurl.com/qa43 , which forwards to 
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12
> -patterns.html#fault-replacement
> 
> 
> -- 
> David Booth
> W3C Fellow / Hewlett-Packard
> Telephone: +1.617.253.1273
> 
> 
>

Received on Thursday, 9 October 2003 11:50:57 UTC