{"id":45,"date":"2002-10-29T11:30:00","date_gmt":"2002-10-29T15:30:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=27"},"modified":"2002-10-29T11:30:00","modified_gmt":"2002-10-29T15:30:00","slug":"what-is-a-message","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2002\/10\/what-is-a-message\/","title":{"rendered":"What is a Message?"},"content":{"rendered":"<p>A couple of recent <a href=\"http:\/\/www.gotdotnet.com\/team\/dbox\/spoutlet.aspx#nn2002-10-23T15:30-08:00\">blogs<\/a> and <a href=\"argh-forgot-but-still-looking-for-it\">messages<\/a> I&#8217;ve seen prompted me to write this.  They both suggest that a &#8220;SOAP message&#8221; is necessarily a &#8220;message&#8221;.  I disagree.<\/p>\n\n<p>When bound to an application protocol, a SOAP message\/envelope is not a message because it doesn&#8217;t contain the necessary information with which to understand what it means.  For example, a SOAP envelope which included a <a href=\"http:\/\/www.hr-xml.org\/channels\/home.htm\">HR-XML<\/a> resume is not a message, because it doesn&#8217;t say what is to be done with the resume; is it to be forwarded on to somebody else?  Submitted as part of a job application?  Meant to update an existing resume?  This is where the envelope of the underlying protocol, such as HTTP comes in; the HTTP request line (method, URI, version), headers, <em>and<\/em> the body which includes the SOAP envelope, forms the entire message.<\/p>\n\n<p>If HTTP were a transport protocol, then a SOAP envelope\/message sent over HTTP would always be a message.  But it isn&#8217;t, it&#8217;s an application protocol.  And please don&#8217;t think this is nitpicking.  Far from it, I believe it&#8217;s the single biggest misunderstanding that has lead us to where we are at with Web services (i.e. a mess).  If people knew what an application protocol was, I think many more (not all, of course) would have thought twice about proceeding with Web services.<\/p>","protected":false},"excerpt":{"rendered":"A couple of recent blogs and messages I&#8217;ve seen prompted me to write this. They both suggest that a &#8220;SOAP message&#8221; is necessarily a &#8220;message&#8221;. I disagree. When bound to an application protocol, a SOAP message\/envelope is not a message because it doesn&#8217;t contain the necessary information with which to understand what it means. For [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[17,26,40],"class_list":["post-45","post","type-post","status-publish","format-standard","hentry","category-uncategorized","tag-mobile","tag-soap","tag-xml"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/45","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=45"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/45\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=45"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=45"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=45"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}