Re: TBTF: nesting

> So you prefer the approach that there can be only one binding in use

Yes.  One reason is that arbitrary mix and match allows a theoretical
NxM set of compositions, when in reality it's most likely [N..N+M]

If everyone took care to provide the same semantics regardless of the
lower layers, it's a no-brainer.  If DIME over BEEP doesn't support the
same things as DIME over HTTP, then let's call that out and make
explicit what the SOAP implementor must do to patch over the differences
so that *SOAP semantics* are the same regardless of the underlying
stack.

	/r$
-- 
Zolera Systems, Securing web services (XML, SOAP, Signatures,
Encryption)
http://www.zolera.com

Received on Thursday, 19 July 2001 23:25:06 UTC