Use of optional HTTP Features (requested Last Call Issue)

Tables 9 [1] and 16 [2] of the latest editors drafts of SOAP 1.2 contain
entries such as:
|----------------+-----------------------------------------------------------------------------------------------------|

| Additional     | Generated in accordance with the rules for the binding
specific expression of any optional features |
| Headers        | in use for this message exchange
|
|----------------+-----------------------------------------------------------------------------------------------------|




IBM is pleased to see these entries but requests that consideration be
given to adding a clarification during last call.

Specifically, IBM requests that a note be added to make clear that features
such as http Content-Encoding [3] may be enabled through use of the
features described in the table entry above.   IBM would like for
content-encoding to be supported when using SOAP over HTTP, and we believe
that the current draft does support it.  We are only requesting that the
spec be made a bit clearer on this point.  Thank you very much.

[1]
http://www.w3.org/2000/xp/Group/2/05/14/soap12-part2-1.93.html#tabreqstateinitfields

[2]
http://www.w3.org/2000/xp/Group/2/05/14/soap12-part2-1.93.html#tabresstaterecheads

[3] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.11

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------

Received on Sunday, 2 June 2002 21:20:23 UTC