- From: Mark Baker <distobj@acm.org>
- Date: Wed, 14 Dec 2005 01:42:03 -0500
- To: www-tag@w3.org
Greetings, Just a quick clarification on something Dave was minuted as saying; "DO: Consider multihop with HTTP first hop and JMS for second. Note that wsa:address is for the ultimate destination, not the intermediate. Mark believes that HTTP prohibits this." The problem is with wsa:To, not wsa:Address per se, as the former is the SOAP header which, when present in a SOAP/HTTP message, supercedes the HTTP Request-URI as the provider of the "ultimate destination" URI. FWIW, this is partly the fault of the default SOAP 1.2 HTTP binding, because it defines the HTTP Request-URI to be the address of the "next hop", not the ultimate destination. I think it's pretty clear (RFC 2616 sec 1.4, amoungst other places) that this is incorrect. Thanks. Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Coactus; Web-inspired integration strategies http://www.coactus.com
Received on Wednesday, 14 December 2005 06:42:51 UTC