{"id":88,"date":"2003-02-02T21:52:00","date_gmt":"2003-02-03T01:52:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=225"},"modified":"2003-02-02T21:52:00","modified_gmt":"2003-02-03T01:52:00","slug":"bosworth-the-next-inflection-point","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2003\/02\/bosworth-the-next-inflection-point\/","title":{"rendered":"Bosworth; The Next Inflection Point"},"content":{"rendered":"

Edwin Khodabakchian reports<\/a>\non an Adam Bosworth presention entitled\nThe Next Inflection Point<\/a>.<\/p>\n\n

Adam’s an extremely bright guy, and I’m fully expecting him to have a\n“REST epiphany” ahead of most others due to both the depth and bredth of his\nexperiences. But while this is an extremely interesting presentation, there are\nsome claims that just don’t synch up with the current approach taken with Web\nservices. In particular, there’s this quote which Edwin pointed out;<\/p>\n\n

\nWe will look back in wonder and ask how we ever survived in the current anarchy where information did not flow as seamlessly and as metered and managed a manner between programs as electricity flows between devices today.\n<\/blockquote>\n\n

Whether or not you agree that Web services are the next big thing, I would\nexpect that most people would see the problems in this statement; data flow with\nWeb services is anything but seamless.<\/p>\n\n

“Seamless data flow” derives from a data flow architectural style in which\ncomponents expose a common (no, not necessarily uniform 8-) interface. The\nexample I’ve used before is\npipe-and-filter<\/a>,\nala Unix, with stdout\/stdin. Non-common (i.e. component-specific) interfaces are\nnotoriously difficult to compose, and therefore anything but seamless, because new glue\ncode has to be written for each set of components that need to be composed (the old\nintegration-complexity argument, O(N^2) or O(NlogN) for Web services vs. O(N) for the\nWeb).<\/p>\n\n

So I’m all for seamless data flow, but Web services simply don’t have it.<\/p>","protected":false},"excerpt":{"rendered":"Edwin Khodabakchian reports on an Adam Bosworth presention entitled The Next Inflection Point. Adam’s an extremely bright guy, and I’m fully expecting him to have a “REST epiphany” ahead of most others due to both the depth and bredth of his experiences. But while this is an extremely interesting presentation, there are some claims that […]","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-88","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/88","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=88"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/88\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=88"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=88"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=88"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}