<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Insights Delimited By Time</title>
	<atom:link href="http://srihari.info/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://srihari.info/blog</link>
	<description>Musings on technology, people</description>
	<pubDate>Sun, 03 Jan 2010 10:30:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
	<language>en</language>
	<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/>		<item>
		<title>HNY</title>
		<link>http://srihari.info/blog/posts/hny/</link>
		<comments>http://srihari.info/blog/posts/hny/#comments</comments>
		<pubDate>Sun, 03 Jan 2010 10:30:29 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=73</guid>
		<description><![CDATA[Came across a significant post by JP Rangaswami (Chief Scientist @BT) reckoning 2010 as the Year of the Platform.
]]></description>
			<content:encoded><![CDATA[<p>Came across a significant post by JP Rangaswami (Chief Scientist @BT) reckoning 2010 as the <a href="http://confusedofcalcutta.com/2009/12/31/life-in-transit-happy-new-year-everyone/">Year of the Platform</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/hny/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Notes on Leadership</title>
		<link>http://srihari.info/blog/posts/notes-on-leadership/</link>
		<comments>http://srihari.info/blog/posts/notes-on-leadership/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 20:02:35 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Insights]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=67</guid>
		<description><![CDATA[Prof. Rosabeth Moss Kanter  draws leadership lessons from the late Edward Kennedy&#8217;s life.
]]></description>
			<content:encoded><![CDATA[<p><a href="http://blogs.harvardbusiness.org/kanter/"><span style="color: #000000; text-decoration: none;">Prof. </span></a><a href="http://blogs.harvardbusiness.org/kanter/">Rosabeth Moss Kanter</a>  draws leadership lessons <a href="http://blogs.harvardbusiness.org/kanter/2009/08/ted-kennedys-leadership-lessons.html">from the late Edward Kennedy&#8217;s life</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/notes-on-leadership/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Hypermedia and pubsubhubbub</title>
		<link>http://srihari.info/blog/posts/hypermedia-and-pubsubhubbub/</link>
		<comments>http://srihari.info/blog/posts/hypermedia-and-pubsubhubbub/#comments</comments>
		<pubDate>Sun, 09 Aug 2009 18:05:25 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Architecture]]></category>

		<category><![CDATA[Design]]></category>

		<category><![CDATA[REST]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=57</guid>
		<description><![CDATA[Last week some folks from Google released a new lightweight publish subscribe protocol called pubsubhubbub  that interestingly also includes a new an ATOM extension. This is one of the first attempts to solve the polling issue that currently plagues feed aggregators such as Friend Feed etc.
At the outset one thing to bear in mind [...]]]></description>
			<content:encoded><![CDATA[<p>Last week some folks from Google released a new lightweight publish subscribe protocol called <strong>pubsubhubbub </strong> that interestingly also includes a new an ATOM extension. This is one of the first attempts to solve the polling issue that currently plagues feed aggregators such as Friend Feed etc.<br />
At the outset one thing to bear in mind is that this is not a mechanism that browser/desktop based  feed subscribers can leverage. For that we will have to wait for Web Sockets to become standard. As far as pubsubhubbub goes you need to be a distributor or an aggregator of some kind to find this useful, very useful indeed.<br />
More information can be found on the project&#8217;s wiki <a href="http://code.google.com/p/pubsubhubbub/wiki/BuildingAHub">but the first 12 slides of this one presentation in particular</a> I think explains the mechanism involved quite succinctly.<br />
For those who want to see this idea in action I recommend <a href="http://googlereader.blogspot.com/2009/08/pubsubhubbub-support-for-reader-shared.html">watching the video where friend feed is shown</a> leveraging this protocol.</p>
<p>What stands out for a REST enthusiast like me is that the way a feed describes its Hub server(s) in its Atom or RSS XML file. This is done via a link relation called <strong>hub(link rel=&#8221;hub&#8221;) </strong>.<br />
Of late there have been many before whom I have had to be quite tongue-tied explaining the possible pragmatic uses of the notion of hypermedia. So you can imagine my excitement on seeing a link relation being used as a significant part of this protocol. In fact all the fun starts with that one link relation. This clearly is a humble beginning to popularize web-style messaging.</p>
<p>Okay&#8230;now I am <a href="http://code.google.com/p/sahaara/">off to build a hub</a>. Should be fun!! Once I have it ready it will be time to convince an enter-pricey architect to use this idea. LOL :)!!!</p>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/hypermedia-and-pubsubhubbub/feed/</wfw:commentRss>
		</item>
		<item>
		<title>HATEOAS Enlightenment</title>
		<link>http://srihari.info/blog/posts/hateoas-enlightenment/</link>
		<comments>http://srihari.info/blog/posts/hateoas-enlightenment/#comments</comments>
		<pubDate>Wed, 01 Apr 2009 17:50:56 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=54</guid>
		<description><![CDATA[Finally some excellent arguments for why HATEOAS. For those interested in the details here is the thread on rest-discuss.
]]></description>
			<content:encoded><![CDATA[<p>Finally some excellent arguments for <a href="http://blogs.sun.com/craigmcc/entry/why_hateoas">why HATEOAS</a>. For those interested in the details <a href="http://tech.groups.yahoo.com/group/rest-discuss/?yguid=352334505">here is the thread on rest-discuss</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/hateoas-enlightenment/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Clay Shirky&#8217;s note on Newspapers</title>
		<link>http://srihari.info/blog/posts/clay-shirkys-note-on-newspapers/</link>
		<comments>http://srihari.info/blog/posts/clay-shirkys-note-on-newspapers/#comments</comments>
		<pubDate>Fri, 27 Mar 2009 16:51:15 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=51</guid>
		<description><![CDATA[There has been some significant discussion on the blogsphere about Clay Shirky&#8217;s recent post on the future (or the lack of it) of news papers. Here is a collection of some of his ideas that appealed a lot to me - 

Revolutions create a curious inversion of perception. In ordinary times, people who do no [...]]]></description>
			<content:encoded><![CDATA[<p>There has been some significant discussion on the blogsphere about Clay Shirky&#8217;s recent post on the future (or the lack of it) of news papers. Here is a collection of some of his ideas that appealed a lot to me - </p>
<blockquote><p>
Revolutions create a curious inversion of perception. In ordinary times, people who do no more than describe the world around them are seen as pragmatists, while those who imagine fabulous alternative futures are viewed as radicals. The last couple of decades haven’t been ordinary, however. Inside the papers, the pragmatists were the ones simply looking out the window and noticing that the real world was increasingly resembling the unthinkable scenario. These people were treated as if they were barking mad. Meanwhile the people spinning visions of popular walled gardens and enthusiastic micropayment adoption, visions unsupported by reality, were regarded not as charlatans but saviors.
</p></blockquote>
<blockquote><p>
&#8230;When reality is labeled unthinkable, it creates a kind of sickness in an industry. Leadership becomes faith-based, while employees who have the temerity to suggest that what seems to be happening is in fact happening are herded into Innovation Departments, where they can be ignored en masse.
</p></blockquote>
<blockquote><p>
Round and round this goes, with the people committed to saving newspapers demanding to know “If the old model is broken, what will work in its place?” To which the answer is: Nothing. Nothing will work. There is no general model for newspapers to replace the one the internet just broke&#8230;.It makes increasingly less sense even to talk about a publishing industry, because the core problem publishing solves — the incredible difficulty, complexity, and expense of making something available to the public — has stopped being a problem.
</p></blockquote>
<blockquote><p>
That is what real revolutions are like. The old stuff gets broken faster than the new stuff is put in its place. The importance of any given experiment isn’t apparent at the moment it appears&#8230;<br />
And so it is today. When someone demands to know how we are going to replace newspapers, they are really demanding to be told that we are not living through a revolution. They are demanding to be told that old systems won’t break before new systems are in place. They are demanding to be told that ancient social bargains aren’t in peril, that core institutions will be spared, that new methods of spreading information will improve previous practice rather than upending it. They are demanding to be lied to.<br />
There are fewer and fewer people who can convincingly tell such a lie.
</p></blockquote>
<blockquote><p>
If you want to know why newspapers are in such trouble, the most salient fact is this: Printing presses are terrifically expensive to set up and to run.This bit of economics, normal since Gutenberg, limits competition while creating positive returns to scale for the press owner, a happy pair of economic effects that feed on each other..
</p></blockquote>
<blockquote><p>
 Any experiment, though, designed to provide new models for journalism is going to be an improvement over hiding from the real, especially in a year when, for many papers, the unthinkable future is already in the past&#8230;..For the next few decades, journalism will be made up of overlapping special cases&#8230;Many of these models will fail. No one experiment is going to replace what we are now losing with the demise of news on paper, but over time, the collection of new experiments that do work might give us the journalism we need.
</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/clay-shirkys-note-on-newspapers/feed/</wfw:commentRss>
		</item>
		<item>
		<title>And the award goes to&#8230;</title>
		<link>http://srihari.info/blog/posts/and-the-award-goes-to/</link>
		<comments>http://srihari.info/blog/posts/and-the-award-goes-to/#comments</comments>
		<pubDate>Fri, 20 Mar 2009 05:45:40 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=49</guid>
		<description><![CDATA[Though its been a couple of days since the award was announced I did not come across a lot of mention of this year&#8217;s ACM Turning Award in the blogsphere except on Mark Little&#8217;s blog.
This year&#8217;s Turing Award (the equivalent of the Noble Prize in computing) has gone to Barbara Liskov for her contributions to [...]]]></description>
			<content:encoded><![CDATA[<p>Though its been a couple of days since the award was announced I did not come across a lot of mention of this year&#8217;s ACM Turning Award in the blogsphere except on <a href="http://markclittle.blogspot.com/">Mark Little&#8217;s</a> blog.</p>
<p>This year&#8217;s <a href="http://news.bbc.co.uk/2/hi/technology/7937010.stm">Turing Award (the equivalent of the Noble Prize in computing) has gone to Barbara Liskov</a> for her contributions to programming. Prof. Liskov was also the first US woman to be awarded a PhD in computing. </p>
<p>Also thanks to Mark, I got hold of a copy of Prof. Liskov&#8217;s paper on <a href="http://portal.acm.org/citation.cfm?id=42399">Argus</a> -  a programming language and system that was developed to support the implementation and execution of distributed programs.</p>
<p>This year is already turning out to be very exciting given that we are seeing people, especially those <a href="http://www.allthingsdistributed.com/2008/12/teamwork.html">from a Distributed Systems background being honored</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/and-the-award-goes-to/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Cloud Computing Clarified</title>
		<link>http://srihari.info/blog/posts/cloud-computing-clarified/</link>
		<comments>http://srihari.info/blog/posts/cloud-computing-clarified/#comments</comments>
		<pubDate>Sat, 21 Feb 2009 16:31:22 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Architecture]]></category>

		<category><![CDATA[Technical Judgement]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=37</guid>
		<description><![CDATA[Finally an authoritative work on Cloud Computing from UC Berkley&#8217;s RAD Labs. It is quite likely that in the time to come other works on cloud computing will end up citing this paper a lot!
Also watch the quick 15 minute video.
]]></description>
			<content:encoded><![CDATA[<p>Finally an <a href="http://berkeleyclouds.blogspot.com/">authoritative work on Cloud Computing</a> from <a href="http://radlab.cs.berkeley.edu/wiki/RAD_Lab">UC Berkley&#8217;s RAD Labs</a>. It is quite likely that in the time to come other works on cloud computing will end up citing this paper a lot!</p>
<p>Also watch the quick 15 minute video.</p>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/cloud-computing-clarified/feed/</wfw:commentRss>
		</item>
		<item>
		<title>SOA India 2008</title>
		<link>http://srihari.info/blog/posts/soa-india-2008/</link>
		<comments>http://srihari.info/blog/posts/soa-india-2008/#comments</comments>
		<pubDate>Fri, 05 Dec 2008 11:18:40 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Architecture]]></category>

		<category><![CDATA[REST]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=32</guid>
		<description><![CDATA[A couple of weeks ago I talked about REST at SOA India 2008. It was nice to see some attendees already familiar with REST mostly because they were consumers of Amazon S3 but were curious to know the details. The talk went well and today I received some requests for the slides. So here is Integrating [...]]]></description>
			<content:encoded><![CDATA[<p>A couple of weeks ago I talked about REST at SOA India 2008. It was nice to see some attendees already familiar with REST mostly because they were consumers of Amazon S3 but were curious to know the details. The talk went well and today I received some requests for the slides. So here is <a href="http://srihari.info/blog/wp-content/uploads/2008/12/rest.pdf">Integrating RESTfully</a>. I intentionally skipped most other constraints of REST and limited myself to the Client Server and Uniform Interface. In retrospect I think it was a good decision as a) the other concepts are fairly well understood and b) with all the arguments and questions Uniform interface ended up taking most of the time.</p>
<div id="__ss_820927" style="width: 425px; text-align: left;"><a style="font:14px Helvetica,Arial,Sans-serif;display:block;margin:12px 0 3px 0;text-decoration:underline;" title="Integrating RESTfully" href="http://www.slideshare.net/srihari.srinivasan/integrating-restfully-presentation?type=powerpoint">Integrating RESTfully</a><object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="425" height="355" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true" /><param name="allowScriptAccess" value="always" /><param name="src" value="http://static.slideshare.net/swf/ssplayer2.swf?doc=rest-1228474393529194-9&amp;stripped_title=integrating-restfully-presentation" /><embed type="application/x-shockwave-flash" width="425" height="355" src="http://static.slideshare.net/swf/ssplayer2.swf?doc=rest-1228474393529194-9&amp;stripped_title=integrating-restfully-presentation" allowscriptaccess="always" allowfullscreen="true"></embed></object> </p>
<div style="font-size: 11px; font-family: tahoma,arial; height: 26px; padding-top: 2px;">View SlideShare <a style="text-decoration:underline;" title="View Integrating RESTfully on SlideShare" href="http://www.slideshare.net/srihari.srinivasan/integrating-restfully-presentation?type=powerpoint">presentation</a> or <a style="text-decoration:underline;" href="http://www.slideshare.net/upload?type=powerpoint">Upload</a> your own. (tags: <a style="text-decoration:underline;" href="http://slideshare.net/tag/rest">rest</a>)</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/soa-india-2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>RESTrospective - Part 1</title>
		<link>http://srihari.info/blog/posts/restrospective-part-1/</link>
		<comments>http://srihari.info/blog/posts/restrospective-part-1/#comments</comments>
		<pubDate>Mon, 10 Nov 2008 21:15:04 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=19</guid>
		<description><![CDATA[


For the last 10 months or so I have been quite heavily involved in building RESTful server components and I think now is an appropriate time to retrospect on how my own thinking has changed since then.
For the first month or so I really did get this cool new stuff called REST or to put [...]]]></description>
			<content:encoded><![CDATA[<div>
<div>
<div>
<p>For the last 10 months or so I have been quite heavily involved in building RESTful server components and I think now is an appropriate time to retrospect on how my own thinking has changed since then.</p>
<p>For the first month or so I really did get this cool new stuff called REST or to put in more succinctly the whole Roy&#8217;s Ph.D. thing was not quite palatable leave alone digesting it <img src='http://srihari.info/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Sam Ruby&#8217;s book certainly helped in getting features of my application delivered in a fairly restful way but the biggest pain was coming to terms with the idea of your components having an Uniform Interface. I had done some XML-RPC and SOAP over the previous year and when compared with it REST seemed very limiting.</p>
<p>The pain is felt more acutely if you are fall into the trap of thinking that your application must do only CRUD and your objects must be devoid of any other behavior. The operation of HTTP&#8217;s uniform interface map very well with CRUD operations on your objects but thinking that every object in your system can have only 4 methods on it did make me say &#8220;WHAT!!!!!&#8221;</p>
<p>Then along came <a href="http://duncan-cragg.org" target="_blank">Duncan Cragg</a> (an ex Thoughtworker himself) and I chanced to read his treatise called The RESTful Dialogues. A must read, notwithstanding its terseness, for anyone trying to get some REST. Of all the episodes the one that I found most profound was the discussion on <a href="http://duncan-cragg.org/blog/post/business-functions-rest-dialogues/" target="_blank">Business Functions</a>. </p>
<p>As an Object programmer I was trained to think that each object is a special creature and therefore was blessed with special powers that were bestowed only unto him. So like children, every object is special to its creator. And within the creator lies this great primordial urge to expose the powers of this super child to the whole network AS IS.</p>
<p>And to top it all the Object Oriented in me was spoilt beyond measure with luxuries of turning something into a distributed service just at the click of a mouse in my favorite programming language/IDE. So all in all I was finding it very hard to come to terms with the idea of a unified &amp; consistent network interface for all network components.</p>
<p>So much that I kept arguing saying posting to  &#8221;http://localhost:300/something/do_this&#8221; and  &#8221;http://localhost:300/something/do_this_also&#8221; and so on was <a href="http://steve.vinoski.net/blog/2008/07/01/convenience-over-correctness/" target="_blank"> so much easier way to web scale nirvana (a.k.a ProgrammerConvenience pattern) than understand this whole uniform interface thing</a>.</p>
<div>I was trained by virtue of my experience with monolithic systems in always trying to get my objects to &#8220;doSomething&#8221; instead of &#8220;helping them transform!&#8221; or help in &#8220;making something so&#8221;.</div>
<p><br/></p>
<div>This shift is perhaps what <a href="http://duncan-cragg.org" target="_blank">Duncan</a> means when he talks about shifting from the Imperative to the Declarative school of thought .</div>
<p><br/></p>
<div>It feels like there is this fundamental thing that you don&#8217;t learn either at school or at work even after spending a lot of time. Its about understanding limitations, on your own! You are never taught to see the limitations of choices you make. We justify and we thus let life ebb away, acting in old ways&#8230;</div>
<p><br/></p>
<div>Apologies for the detour.Let me get to the point.</div>
<p><br/></p>
<div>The point is a style may fit well for doing domain objects with rich behavior in a local setting. But when we start unconsciously using this style for building distributed systems we have taken for granted, the appropriateness of this style for a hard problem like distribution. By doing this we have in fact not even acknowledged distribution as an existing problem.</div>
<p><br/></p>
<div>True, habits die hard.</div>
<p><br/></p>
<div>Personally for me without this nearly 15 years old work that has such an <a href="http://research.sun.com/techrep/1994/abstract-29.html" target="_blank">unassuming title</a> I would not have understood what distribution is all about.
</div>
<div>
Creating special purpose behavior is one thing but distributing them is another. Don&#8217;t mix the two up with annotations.
</div>
<p><br/></p>
<div>More later.</div>
</div>
</div>
</div>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/restrospective-part-1/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Another miss</title>
		<link>http://srihari.info/blog/posts/another-miss/</link>
		<comments>http://srihari.info/blog/posts/another-miss/#comments</comments>
		<pubDate>Sun, 06 Jul 2008 08:19:35 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
		
		<category><![CDATA[Design]]></category>

		<category><![CDATA[Technical Judgement]]></category>

		<guid isPermaLink="false">http://srihari.info/blog/?p=16</guid>
		<description><![CDATA[Somewhere I heard the speaker say in a ppt on REST that the guys behind the WS-* specs are ** actually bright ** people but somehow kept missing the point. Here is another proof of this statement.
I think this juggernaut won&#8217;t stop until they have made everything that HTTP facilitates also possible through SOAP. Way to go [...]]]></description>
			<content:encoded><![CDATA[<p>Somewhere I heard the speaker say in a ppt on REST that the guys behind the WS-* specs are ** actually bright ** people but somehow kept missing the point. <a title="This one" href="http://www.mnot.net/blog/2008/07/04/a_new_dread" target="_blank">Here is another proof</a> of this statement.</p>
<p>I think this juggernaut won&#8217;t stop until they have made everything that HTTP facilitates also possible through SOAP. Way to go dudes!!</p>
]]></content:encoded>
			<wfw:commentRss>http://srihari.info/blog/posts/another-miss/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
