{"id":266,"date":"2004-01-30T06:23:00","date_gmt":"2004-01-30T10:23:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=245"},"modified":"2004-01-30T06:23:00","modified_gmt":"2004-01-30T10:23:00","slug":"now-departing-grid-next-stop-web","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2004\/01\/now-departing-grid-next-stop-web\/","title":{"rendered":"Now departing Grid. Next stop, Web."},"content":{"rendered":"

Via Savas<\/a> (subscribed!), I’m following\na lot of the discussion regarding the recent Grid\/Web-services “unification” specs,\nWSRF<\/a>. Good stuff! These folks are even closer\nto having their Web gestalt moment I believe, as they’re now talking about\n“stateful resources” (now\nwhere<\/a>\nhave I heard of those before?) in the context of integrating two different systems,\nthe Grid and Web services. Rock on! I think I’ll sign up to a mailing list or two.<\/p>\n\n

While following those links, I ran across a proposal by Savas and his group\ncalled WS-GAF<\/a>, a sort of accidental\nprecursor to parts of WSRF. It mentioned REST;<\/p>\n\n

\nThere have been proposals for naming and uniformly providing access to resources, like the REpresentational State Transfer (REST) [2] model. However, since REST depends on HTTP it is protocol specific and hence unsuitable for heterogeneous systems like the Grid.\n<\/blockquote>\n\n

First, I just want to say that I think it’s wonderful that REST was even\nmentioned in the context of the Grid. Most folks think it’s still just for\nhumans and browsers and HTML. Very refreshing. Now for the bad news (come on,\nyou knew it was coming … 8-). REST does not depend on HTTP at all. It is\nan architectural style<\/em>, and therefore prescribes no specific\nimplementation, it just describes the constraints that one uses when designing\na RESTful system. You could run out and build one that didn’t use\nany existing technology, if you\nwanted to<\/a>.<\/p>\n\n

Savas might be interested in a\nresponse<\/a>\nof mine to\nWerner Vogels<\/a>\nregarding his\nWeb services are not distributed objects<\/a> paper.<\/p>\n\n

WS-GAF still uses URIs, which is great. Here’s an example of one;<\/p>\n\n

\nurn:dais:dataset:b4136aa4-2d11-42bd-aa61-8e8aa5223211\n<\/blockquote>\n\n

This is wonderful, in a sense. It’s the first time I’ve seen that we’ve narrowed\nthe whole SOA\/REST\/Web issue down to an issue of Web architecture, in particular,\nhttpRange-14<\/a>\n(well, you have to squint a little to see why it’s really that issue – it could\nhave been called the “uriRange” issue, i.e. what can a URI identify?).<\/p>\n\n

So my claim is that WS-GAF would be far better off to identify its resources\nusing http URIs, for the same\nreason that “info” scheme users would<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"Via Savas (subscribed!), I’m following a lot of the discussion regarding the recent Grid\/Web-services “unification” specs, WSRF. Good stuff! These folks are even closer to having their Web gestalt moment I believe, as they’re now talking about “stateful resources” (now where have I heard of those before?) in the context of integrating two different systems, […]","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-266","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/266","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=266"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/266\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=266"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}