{"id":429,"date":"2004-08-05T08:14:00","date_gmt":"2004-08-05T12:14:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=447"},"modified":"2004-08-05T08:14:00","modified_gmt":"2004-08-05T12:14:00","slug":"wonder","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2004\/08\/wonder\/","title":{"rendered":"Wonder"},"content":{"rendered":"<p><a href=\"http:\/\/seanmcgrath.blogspot.com\/archives\/2004_08_01_seanmcgrath_archive.html#109169269507360909\">Sean discovers WS-MessageDelivery<\/a>\nwhich triggers him to display a level of frustration that I didn&#8217;t expect to see, but\nthat I&#8217;m happy about.  We need more integration gurus to raise their hands and ask\n&#8220;Hello, what the $%@! are you people doing?!&#8221;, in the hope that those building this\narchitecture may stop to take the time to think about what they&#8217;ve created and give\nit the principled architectural examination it requires.  Sean writes;<\/p>\n\n<blockquote>\nYou started at the wrong end of the pipe. SOAP always was and always will be and API-centric worldview.\n\nThat is not the future.\n\nThat is the past.\n\nRe-implemented badly.\n\nSometimes I wonder. I really do.\n<\/blockquote>\n\n<p>I disagree that SOAP requires an API-centric worldview &#8211; I battled against\nenormous odds to ensure SOAP 1.2 didn&#8217;t &#8211; but I certainly agree that this is\nhow Web services proponents and specs are using the\n<a href=\"http:\/\/www.w3.org\/TR\/soap\">SOAP specs<\/a>.<\/p>\n\n<p>On the other hand, to their credit, Web services promoters <em>are<\/em>\ntrying to distance themselves from APIs.  The problem is that they think\nthey&#8217;ve done this with &#8220;document oriented SOAP&#8221; by removing the operation\nfrom the message.  Unfortunately though, in their architecture, the operation\n<em>is<\/em> still in effect, it&#8217;s just hidden from the message which actually\nmakes things\n<a href=\"http:\/\/www.markbaker.ca\/2002\/09\/Blog\/2004\/03\/09#2004-03-operation\"><em>worse<\/em> than RPC<\/a>\n(in case you wondered if that was possible!).<\/p>\n\n<p>What Web services need is an architecture based <em>purely<\/em> on document\nexchange, not some RPC\/document bastard.  Luckily,\n<a href=\"http:\/\/www.w3.org\/WWW\/\">one<\/a> is readily available.<\/p>","protected":false},"excerpt":{"rendered":"Sean discovers WS-MessageDelivery which triggers him to display a level of frustration that I didn&#8217;t expect to see, but that I&#8217;m happy about. We need more integration gurus to raise their hands and ask &#8220;Hello, what the $%@! are you people doing?!&#8221;, in the hope that those building this architecture may stop to take the [&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-429","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\/429","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=429"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/429\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=429"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=429"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=429"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}