{"id":254,"date":"2004-01-11T19:00:00","date_gmt":"2004-01-11T23:00:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=257"},"modified":"2004-01-11T19:00:00","modified_gmt":"2004-01-11T23:00:00","slug":"don-box-on-rest","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2004\/01\/don-box-on-rest\/","title":{"rendered":"Don Box on REST"},"content":{"rendered":"

A nice post<\/a>\nfrom Don last weekend, addressing the “roach motel” (aka “application silo”) problem,\nand what Longhorn’s doing to help developers who want to avoid it. Some comments;<\/p>\n\n

\nThough I think their characterization of RPC is a bit naïve (NFS is a great counterexample of a broadly adopted RPC protocol), the argument in favor of common operations is a strong one that I’m extremely sympathetic to (watch this space).\n<\/blockquote>\n\n

NFS is built on an RPC infrastructure, but it’s not what you’d call RPC because\nits users don’t define the interface<\/em>, the\nprotocol<\/a> does. Consider that\njust because it’s built with RPC, you don’t see it integrated with other\nRPC based services. I think there’s an important lesson there.<\/p>\n\n

\nWhat the REST argument conveniently sidesteps is that had it not been for HTML (a common schema), HTTP (a common set or operations\/access mechanisms) would have never registered on most people’s radar.\n<\/blockquote>\n\n

I don’t know about others, but I’ve never side-stepped that issue. I’m\nquite up front when I claim that REST alone doesn’t address the “schema\nexplosion” problem, and that HTML is only a “unifying schema” for humans. I\ncommonly follow that up with an explanation of\nwhy I like Semantic Web technologies<\/a>,\nas they extend the Web to address the explosion problem for automata.<\/p>\n\n

Anyhow, I’m very encouraged by the positive feedback, and will be\nkeenly “watching that space”! Thanks, Don.<\/p>","protected":false},"excerpt":{"rendered":"A nice post from Don last weekend, addressing the “roach motel” (aka “application silo”) problem, and what Longhorn’s doing to help developers who want to avoid it. Some comments; Though I think their characterization of RPC is a bit naïve (NFS is a great counterexample of a broadly adopted RPC protocol), the argument in favor […]","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-254","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/254","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=254"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/254\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=254"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=254"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=254"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}