W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2003

Re: Streaming and Well-Formedness

From: Marc Hadley <Marc.Hadley@Sun.COM>
Date: Tue, 01 Apr 2003 14:05:15 -0500
To: Mark Baker <mbaker@idokorro.com>
Cc: Noah Mendelsohn/Cambridge/IBM <noah_mendelsohn@us.ibm.com>, xml-dist-app@w3.org
Message-id: <DF7646E5-6474-11D7-AF8A-0003937568DC@sun.com>

On Tuesday, Apr 1, 2003, at 13:20 US/Eastern, Mark Baker wrote:
> It's my understanding that you shouldn't be chucking mU faults, or 
> doing
> any processing for that matter, until the envelope has been determined
> to
> be well formed.
I'm not sure the spec says that, in fact:

"A message may contain or result in multiple errors during processing. 
Except where the order of detection is specifically indicated (as in 
2.4 Understanding SOAP Header Blocks), a SOAP node is at liberty to 
reflect any single fault from the set of possible faults prescribed for 
the errors encountered. The selection of a fault need not be predicated 
on the application of the "MUST", "SHOULD" or "MAY" keywords to the 
generation of the fault, with the exception that if one or more of the 
prescribed faults is qualified with the "MUST" keyword, then any one 
fault from the set of possible faults MUST be generated."

So I think my service would be at liberty to return a mustUnderstand 
fault even if the envelope turned out to be not well formed (provided 
of course a mustUnderstand fault was also appropriate)


>> -----Original Message-----
>> From: Marc Hadley [mailto:Marc.Hadley@Sun.COM]
>> Sent: Tuesday, April 01, 2003 9:49 AM
>> To: Noah Mendelsohn/Cambridge/IBM
>> Cc: xml-dist-app@w3.org
>> Subject: Re: Streaming and Well-Formedness
>> I agree that there are cases where streaming is difficult, but there
>> are some cases where streaming is useful. E.g. a receiver can send a
>> mustUnderstand fault without waiting for the (potentially large) body
>> of the incoming message to be completely received.
>> Regards,
>> Marc.
Marc Hadley <marc.hadley@sun.com>
Web Technologies and Standards, Sun Microsystems.
Received on Tuesday, 1 April 2003 14:05:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:23 UTC