{"id":264,"date":"2004-01-28T05:02:00","date_gmt":"2004-01-28T09:02:00","guid":{"rendered":"http:\/\/www.markbaker.ca\/wp\/?p=247"},"modified":"2004-01-28T05:02:00","modified_gmt":"2004-01-28T09:02:00","slug":"beep-vs-web-hacks","status":"publish","type":"post","link":"http:\/\/www.markbaker.ca\/blog\/2004\/01\/beep-vs-web-hacks\/","title":{"rendered":"BEEP vs. Web &#34;hacks&#34;"},"content":{"rendered":"<p><a href=\"http:\/\/webpages.charter.net\/chrisfer\/archives\/2004_01_01_oldrants.html#107529903741007073\">Chris Ferris writes<\/a>,\nregarding BEEP and HTTP;<\/p>\n\n<blockquote>\nThe BEEP protocol offers much richer message exchange patterns than does HTTP, enabling the likes of publish\/subscribe, one request\/N responses, etc. without having to resort to hacks.\n<\/blockquote>\n\n<p>I&#8217;m not a fan of BEEP, primarily because I see little value in standardizing\nat that layer (OSI layers 5 and 6) without standardizing up higher with an\napplication protocol, because <a href=\"http:\/\/www.ics.uci.edu\/~rohit\/L7-1.html\">layer 7<\/a>\nis where interop happens on the Internet.<\/p>\n\n<p>But I have to take issue with the &#8220;hacks&#8221; jab.  He and I went back and forth on\nat least one HTTP extension in the early days of the\n<a href=\"http:\/\/www.w3.org\/2002\/ws\/arch\/\">Web Services Architecture WG<\/a>; the\n<a href=\"http:\/\/lists.w3.org\/Archives\/Public\/www-ws-arch\/2002May\/0024.html\">MONITOR method<\/a>.\nIs that a hack?  Is <a href=\"http:\/\/www.mod-pubsub.org\/\">mod-pubsub<\/a>\na hack? (well, parts sure are, but the bulk of it? 8-)<\/p>\n\n<p>I suppose if you have the luxury of working in a greenfield environment with little\nin the way of architectural constraints (e.g. BEEP), then you can pretty much do what you\nwant, and perhaps you&#8217;ll end up with something quite elegant.  But doing the same thing\nwith an existing architecture is <em>much<\/em> harder because you have more constraints\nyou have to work within.  That doesn&#8217;t make them hacks.<\/p>","protected":false},"excerpt":{"rendered":"Chris Ferris writes, regarding BEEP and HTTP; The BEEP protocol offers much richer message exchange patterns than does HTTP, enabling the likes of publish\/subscribe, one request\/N responses, etc. without having to resort to hacks. I&#8217;m not a fan of BEEP, primarily because I see little value in standardizing at that layer (OSI layers 5 and [&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-264","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/264","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=264"}],"version-history":[{"count":0,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/posts\/264\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/media?parent=264"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/categories?post=264"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.markbaker.ca\/blog\/wp-json\/wp\/v2\/tags?post=264"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}