MustUnderstand = 'true'
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 ?
[Simon Fell]
Axis will fault if the client receives a non-understood mU='1' header. Being a huge Orthogonal Extensibility fan, I'm pushing for this behaviour any time I talk to other implementers within or outside Macromedia. This is an interesting case, though, in that the MU fault is very useful as a negotiation tool when it is emitted by a server - the client can look at what was misunderstood (at least in SOAP 1.2) and have a much better chance of resending a message which works. When the MU fault is generated on the client side, however, the server has no clue that something it sent was misunderstood, and we have to rely on some higher-level means of negotiation in order to get a better result with a future request. This would be an interesting use-case for transport protocols like BEEP, which keeps an open two-way channel instead of being bound to a single request/response pair.
8:25:50 AM 
|
|
