W3C home > Mailing lists > Public > xml-dist-app@w3.org > July 2001

Re: Infoset based rewrite of SOAP Section 4

From: <Noah_Mendelsohn@lotus.com>
Date: Mon, 2 Jul 2001 11:31:59 -0400
To: christopher ferris <chris.ferris@east.sun.com>
Cc: mnot@mnot.net, xml-dist-app@w3.org
Message-ID: <OF891A358D.1CDD97E0-ON85256A7D.00553D19@lotus.com>
Chris Ferris writes:

>> How is the serialization mechanism 
>> conveyed from the sender to receiver.

Simple answer:  as is already the case, sender and receiver need to agree 
on the binding being used.   Remember, we are basically talking about 
whether we are using HTTP, SMTP, or something else.  In a lot of cases, we 
will know that before we even install the system.  If you are looking for 
a more dynamic contract, then description languages such as WSDL give you 
a way to advertise bindings for dynamic access. 

The point is, most individual bindings will choose one representation or 
another for the XML to be transmitted.  Some may be more flexible and 
others.  For example, my binding to SMTP might indicate in its 
specification that all envelopes are transmitted as well formed XML, UTF-8 
only.   Your binding to HTTP might specify a choice of UTF-8 or UTF-16, to 
be determined by the content type header.  A third binding might indicate 
"if you're doing SOAP over orange juice cans and strings, then we always 
use (whatever) compressed representation". 

In summary:  you find out the binding in the usual SOAP ways.  The binding 
specification tells you what representation will be used, and if options 
are offered, how to determine at runtime which option is being used.

Noah Mendelsohn                                    Voice: 1-617-693-4036
Lotus Development Corp.                            Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
Received on Monday, 2 July 2001 11:37:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:14 UTC