- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 18 Sep 2001 17:07:46 -0700
- To: XML Distributed Applications List <xml-dist-app@w3.org>
(for inclusion in the binding framework) Binding to Application-Specific Protocols Some underlying protocols may be designed for a particular purpose or application profile. SOAP bindings to such protocols MAY use the same endpoint identification (e.g., TCP port number) as the underlying protocol, in order to reuse the existing infrastructure associated that protocol. However, the use of well-known ports by SOAP may incur additional, unintended handling by intermediaries and underlying implementations. For example, HTTP is commonly thought of as a 'Web browsing' protocol, and network administrators may place certain restrictions upon its use, or may interpose services such as filtering, content modification, routing, etc. Often, these services are interposed using port number as a heuristic. As a result, binding definitions which use these protocols SHOULD document this status, and SHOULD illustrate the use of the binding on a non-default port as a means of avoiding unintended interaction with such services. -- Mark Nottingham http://www.mnot.net/
Received on Tuesday, 18 September 2001 20:07:47 UTC