tag:blogger.com,1999:blog-7618276.post114279291753983909..comments2024-03-14T05:19:03.379-05:00Comments on Koranteng's Toli: The REST Elevator PitchKorantenghttp://www.blogger.com/profile/05280138409675883100noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7618276.post-1143546801438144212006-03-28T05:53:00.000-06:002006-03-28T05:53:00.000-06:00Responding to "Anonymous"'s queries.1. I hope that...Responding to "Anonymous"'s queries.<BR/><BR/>1. I hope that some of the other pitches I've pointed out by the two Tims, Berners-Lee and Bray, are easier to understand. They certainly use less flowery language than me but it is just variations on a theme.<BR/><BR/>If you are more inclined to show rather than tell, you can do no worse than look at Joe Gregario's <A HREF="http://www.xml.com/pub/au/225" REL="nofollow">Restful Web column</A>. They are all essential but <A HREF="http://www.xml.com/pub/a/2005/03/02/restful.html" REL="nofollow">this one gets at the heart of the matter</A>. Paul Prescod, Mark Baker and Sam Ruby have great material also. Alternatively look at Roy Fielding's works. <BR/><BR/>If not, I would try <A HREF="http://koranteng.blogspot.com/2005/06/rest-web-style.html" REL="nofollow">the presentation</A> I delivered last year in which I tried to distill the style. Particularly <A HREF="http://home.comcast.net/~amaah/restweb/index57.htm" REL="nofollow">this slide</A> where I tried to boil down everything into the essentials. I called this model, ArRESTed Development, (I need to find a better name for it). The salient features of this model of development in the web style are:<BR/><BR/>* Resource Modeling<BR/> * Every important resource should be identified<BR/>* Use the right verb<BR/> * Don't abuse HTTP<BR/> * Your users will hate you if you do<BR/> * Life is easier with the web<BR/>* Respect browser conventions<BR/> * Bookmark, Back button, Refresh<BR/>* Layer Stripping & Radical Simplification<BR/><BR/>That last bullet is simply a plea for reducing complexity in software<BR/><BR/>2. The Hi-Lo formulation means something different depending on whoever brandishes it which is why I believe it is a rathole and red herring. Ryan took it to mean something quite subtle but others are far less discriminating. The less said the better.<BR/><BR/>3. hypermedia of course can be in any format as you note.Korantenghttps://www.blogger.com/profile/05280138409675883100noreply@blogger.comtag:blogger.com,1999:blog-7618276.post-1143489936775635072006-03-27T14:05:00.000-06:002006-03-27T14:05:00.000-06:00First, sorry, but that elevator pitch is totally u...First, sorry, but that elevator pitch is totally unintelligible to me.<BR/><BR/>Second, is this whole current Hi vs. Lo crisis solely concerned with whether or not PUT is used (who DELETEs?)?<BR/><BR/>Finally, it's correct that the format of the payloads can vary. For GETs, you might use URIs, querystrings, YAML or XML. For responses, XML or JSON might be approriate. Whatever.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7618276.post-1142841996029393762006-03-20T02:06:00.000-06:002006-03-20T02:06:00.000-06:00Excellent trip Koranteng and I agree for the most ...Excellent trip Koranteng and I agree for the most part. Often times in conversation I find myself refering to the "low-REST" subset, not necessarily to pitch it or recommend it, but rather just to acknowledge its existence or to point out that REST, in some concrete form, has been proven to be highly adoptable. I wouldn't include high/low REST terminology if I was introducing the concept to someone but I find that it's useful keeping discussions going with people who aren't new to the topic. I don't like the idea that conversations are stopping because we lack the vocabulary to have them.<BR/><BR/>PS: I don't know who's telling you to "save it for the book" but it sure isn't me :) Take a page out of Paul Graham's book (no pun intended) and turn the blog into the book verbatim.Anonymousnoreply@blogger.com