{"id":475,"date":"2004-09-29T00:52:00","date_gmt":"2004-09-29T04:52:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/2004\/09\/29\/do-we-need-service-specific-interfaces\/"},"modified":"2004-09-29T00:52:00","modified_gmt":"2004-09-29T04:52:00","slug":"do-we-need-service-specific-interfaces","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2004\/09\/do-we-need-service-specific-interfaces\/","title":{"rendered":"Do we need service specific interfaces?"},"content":{"rendered":"<p><a href=\"http:\/\/www.pacificspirit.com\/blog\/2004\/09\/28\/web_services_needs_transfer_protocols_and_specific_protocols\">Dave Orchard thinks so<\/a>.<\/p>\n\n<p>But hold the phones!  Along the way, we learn this;<\/p>\n\n<blockquote>\nRead operations using a generic protocol (ie GET) hits the 90\/10 point\n<\/blockquote>\n\n<p>Woohoo!  Preach it, brother!<\/p>\n\n<p>But you knew it wasn&#8217;t going to end there&#8230;8-)  He goes on to defend\nthe need for service-specific write interfaces with an example.<\/p>\n\n<p>Without getting into the details of that example since they&#8217;re reasonably\ncomplex, I certainly agree that one can, without too much trouble, find\ncases where uniform semantics are more trouble than they&#8217;re worth.  But\nso what?  Did anybody ever doubt this was the case?  I&#8217;ve\n<a href=\"http:\/\/www.markbaker.ca\/2002\/09\/Blog\/2004\/04\/30#2004-04-restful-jeff\">repeatedly<\/a>\n<a href=\"http:\/\/www.markbaker.ca\/2002\/09\/Blog\/2004\/09\/19#2004-09-champion-conflict\">stated<\/a>\n(and long before too, though I can&#8217;t dig up any refs right now) that it was, including\nmentioning that I&#8217;ve had to use non-uniform semantics on occasion.<\/p>\n\n<p>I think the question David really needs to answer is this; do we need\nspecific write interface semantics like &#8220;orderBook&#8221;, &#8220;hirePerson&#8221;, &#8220;reserveFlight&#8221;,\netc..?  I don&#8217;t think we do; I think POST suffices for all three.<\/p>\n\n<p>Also, I wonder if Dave would like to augment his\n<a href=\"http:\/\/lists.w3.org\/Archives\/Public\/www-ws-arch\/2003Feb\/0055.html\">architectural description of the SOA style<\/a>\nto include an interface constraint, even if it&#8217;s just for reads?<\/p>","protected":false},"excerpt":{"rendered":"Dave Orchard thinks so. But hold the phones! Along the way, we learn this; Read operations using a generic protocol (ie GET) hits the 90\/10 point Woohoo! Preach it, brother! But you knew it wasn&#8217;t going to end there&#8230;8-) He goes on to defend the need for service-specific write interfaces with an example. Without getting [&hellip;]","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-475","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/475","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=475"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/475\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=475"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=475"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}