Simon Fell > Its just code > mustUnderstand='1'

Is the linchpin of SOAP's extensibility model. If you're doing ASP.NET based web services, run don't walk and go read Tim's latest article on mandatory headers. I've pointed out in the past that the default for how mU='1' is handled in ASP.NET is wrong, and is the reason why ASP.NET still shows a failure for the MustUndertand=true interop test. Lets face it, if a MSFT authored service can't get it right, what hope is there for the rest of us ?

Of course I should point out that a number of other toolkits fail the test, and that PocketSOAP doesn't do anything specific if it receives a response with an mU='1', however 4s4c does the right thing. I haven't seen discussed the expected behavior for WS clients handling mU='1' anyone know what the popular toolkits do ?