{"id":141,"date":"2003-07-16T02:20:00","date_gmt":"2003-07-16T06:20:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=172"},"modified":"2003-07-16T02:20:00","modified_gmt":"2003-07-16T06:20:00","slug":"ws-addressing-vs-ws-routing","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2003\/07\/ws-addressing-vs-ws-routing\/","title":{"rendered":"WS-Addressing vs. WS-Routing"},"content":{"rendered":"<p>I&#8217;ve always considered WS-Routing to be one of the few shining stars\nof the WS-* spec family.  Conversely, I&#8217;ve\n<a href=\"http:\/\/www.markbaker.ca\/2002\/09\/Blog\/2003\/03\/13#2003-03-ws-insanity\">said before<\/a>\nthat I consider WS-Addressing to be perhaps the biggest waste of time yet\ndeveloped.  So imagine my surprise when\n<a href=\"http:\/\/www.collaxa.com\/radio\/2003\/07\/15.jsp#a407\">Edwin notes<\/a>\n<a href=\"http:\/\/msdn.microsoft.com\/webservices\/building\/wse\/default.aspx?pull=\/library\/en-us\/dnwebsrv\/html\/programwse2.asp#programwse2_topic4\">this passage<\/a>\nfrom Microsoft&#8217;s WSE 2.0;<\/p>\n\n<blockquote>\nOne of the changes between WSE 1.0 and WSE 2.0 is the support for WS-Addressing. WS-Addressing largely replaces the capabilities of the WS-Routing specification that was supported in WSE 1.0. Instead of focusing on routing paths, WS-Addressing functionally provides a mechanism for adding To and From headers to a SOAP envelope.\n<\/blockquote>\n\n<p>WS-Routing uses URIs for endpoint and intermediary identification, whereas\nWS-Addressing exists because apparently URIs were considered deficient as\nidentifiers.   If you buy WS-Addressing&#8217;s premise (I don&#8217;t, surprise), this\nmakes sense, sort of.  But then you&#8217;re missing the value-add of WS-Routing and its\nsupport for SOAP intermediaries.  The WSE 2.0 use of WS-Addressing defines a much\nless general routing infrastructure, premised upon only ever using gateways (where\nmessages must terminate) rather than <em>both<\/em> gateways and proxies as\nWS-Routing supports.<\/p>","protected":false},"excerpt":{"rendered":"I&#8217;ve always considered WS-Routing to be one of the few shining stars of the WS-* spec family. Conversely, I&#8217;ve said before that I consider WS-Addressing to be perhaps the biggest waste of time yet developed. So imagine my surprise when Edwin notes this passage from Microsoft&#8217;s WSE 2.0; One of the changes between WSE 1.0 [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[26],"class_list":["post-141","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-soap"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/141","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/comments?post=141"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/141\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=141"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=141"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=141"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}