- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 5 Jul 2001 18:53:00 -0800
- To: <eamon.otuathail@clipcode.com>, "Williams, Stuart" <skw@hplb.hpl.hp.com>
- Cc: <xml-dist-app@w3.org>
> If the underlying protocol merely transports the bits (e.g. TCP) - who > describes ... session establishment (where to connect to), how transport > security is provisioned, what are the rules for authentication, what support > is there for intermediaries (e.g. to get through firewalls - [not talking > about SOAP intermediaries here]), how errors are reported (of the underlying > protocol - not SOAP Faults) etc., etc. ALL of these things can be provided by underlying protocols, in-message SOAP blocks, pre-arranged convention, voodoo or a combination of these sources. From SOAP's point of view, all that it knows is that something is underneath it which a) encapsulates it The 'thing beneath' (my currently favoured term ;) also b) might provide services to the users of the soap message c) might impose restrictions on how it can be used Notice that these things don't affect the message itself; just how it is used.
Received on Thursday, 5 July 2001 14:53:22 UTC