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

Re: final decision on well-formedness checking

From: James M Snell <jasnell@us.ibm.com>
Date: Wed, 7 May 2003 10:11:58 -0700
To: "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>
Cc: xml-dist-app@w3.org
Message-ID: <OFB1630691.01C60379-ON88256D1F.005E537E-88256D1F.005E7B48@us.ibm.com>

A yell from the sidelines: +1 !  Things would be much easier if 
well-formedness checking was not a requirement.

- James M Snell
  jasnell@us.ibm.com
  http://www.ibm.com
  (877) 511-5082 / Office
  930-1979 / Tie Line



"Sanjiva Weerawarana" <sanjiva@watson.ibm.com> 
Sent by: xml-dist-app-request@w3.org
05/06/2003 11:49 PM

To
<xml-dist-app@w3.org>
cc

Subject
final decision on well-formedness checking







What was the final verdict from the discussion on whether a SOAP
impl needs to do well-formedness checking? 

I would prefer if one could respond with a non well-formed 
response for bad requests such as those rather than to force every
implementation to walk thru the whole message before doing anything.
Streaming is dammed in that case.

It seems to me that non well-formed requests are VERY unlikely
(especially on TCP style streaming/reliable transports) except
in the case of major SOAP stack bugs. Forcing well-formedness
checking would cut out a major perf improvement opportunity to
cover a case that's way off the 80-20 or 90-10 or even 95-5 split.

Thanks,

Sanjiva.
Received on Wednesday, 7 May 2003 13:22:03 GMT

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