<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Serendipitous Reuse</title>
	<atom:link href="http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/feed/" rel="self" type="application/rss+xml" />
	<link>http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/</link>
	<description>Ask forgiveness, not permission.</description>
	<lastBuildDate>Mon, 15 Mar 2010 14:06:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Betamax in an SOW(orld) - Service Endpoint</title>
		<link>http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/comment-page-1/#comment-558</link>
		<dc:creator>Betamax in an SOW(orld) - Service Endpoint</dc:creator>
		<pubDate>Tue, 29 Jan 2008 04:03:55 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/#comment-558</guid>
		<description>[...] is really the key, that REST has going for it is&#8230; Adoption! What Steve Vinoski terms &#8220;Serendipitous reuse&#8220;. Developing RESTful applications is agile and allows for iterative development; to a large [...]</description>
		<content:encoded><![CDATA[<p>[...] is really the key, that REST has going for it is&#8230; Adoption! What Steve Vinoski terms &#8220;Serendipitous reuse&#8220;. Developing RESTful applications is agile and allows for iterative development; to a large [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#8220;Serendipitous&#8221; Readings - Service Endpoint</title>
		<link>http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/comment-page-1/#comment-529</link>
		<dc:creator>&#8220;Serendipitous&#8221; Readings - Service Endpoint</dc:creator>
		<pubDate>Fri, 25 Jan 2008 04:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/#comment-529</guid>
		<description>[...] to read an interesting article by Steve Vinoski. After graduating from the school of SOAP I&#8217;ve always wondered what was so [...]</description>
		<content:encoded><![CDATA[<p>[...] to read an interesting article by Steve Vinoski. After graduating from the school of SOAP I&#8217;ve always wondered what was so [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is JAX-RS (Restful Java) just another IDL? &#171; Angry Bill</title>
		<link>http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/comment-page-1/#comment-505</link>
		<dc:creator>Is JAX-RS (Restful Java) just another IDL? &#171; Angry Bill</dc:creator>
		<pubDate>Mon, 21 Jan 2008 22:44:15 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/#comment-505</guid>
		<description>[...] on how some think REST requires a definition language like WSDL or IDL. He first mentions it within Serendipitous Reuse, and further expands on it in the blogs Lying Through Their Teeth: Easy vs. Simple, IDL vs. Human [...]</description>
		<content:encoded><![CDATA[<p>[...] on how some think REST requires a definition language like WSDL or IDL. He first mentions it within Serendipitous Reuse, and further expands on it in the blogs Lying Through Their Teeth: Easy vs. Simple, IDL vs. Human [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Subbu Allamaraju</title>
		<link>http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/comment-page-1/#comment-481</link>
		<dc:creator>Subbu Allamaraju</dc:creator>
		<pubDate>Fri, 18 Jan 2008 18:34:10 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/#comment-481</guid>
		<description>Hi Steve,

I just had a chance to read your IEEE paper. Congrats, it is well-written. However, I do have some comment on your analysis.

I don&#039;t think the point that specialized interfaces inhibit reuse does not necessarily lead to the conclusion that &quot;reducing interface differentiation&quot; promotes reuse. Uniformity of interfaces lowers the barrier of entry for application development, but what promotes reuse is, in my opinion, the nature of the problem being solved by an interface. The more specific the problem is, the less likely it is to be reused. The most popular REST/HTTP APIs publicly available today are also solving hard problems that are expensive and time-consuming for everyone to replicate.

Secondly, uniform interface are not necessarily semantically richer than &quot;as generic as possible&quot; interfaces or even &quot;specialized&quot; interfaces. For instance, a RESTful version of your example &quot;BagOfBytes processThis(BagOfBytes)&quot; would not provide all the semantics of the data and context for a client application to use it.

I have a longish comment at &lt;a href=&quot;http://www.subbu.org/weblogs/main/2008/01/comments_on_ser.html&quot; rel=&quot;nofollow&quot;&gt;my blog&lt;/a&gt;.

Subbu</description>
		<content:encoded><![CDATA[<p>Hi Steve,</p>
<p>I just had a chance to read your IEEE paper. Congrats, it is well-written. However, I do have some comment on your analysis.</p>
<p>I don&#8217;t think the point that specialized interfaces inhibit reuse does not necessarily lead to the conclusion that &#8220;reducing interface differentiation&#8221; promotes reuse. Uniformity of interfaces lowers the barrier of entry for application development, but what promotes reuse is, in my opinion, the nature of the problem being solved by an interface. The more specific the problem is, the less likely it is to be reused. The most popular REST/HTTP APIs publicly available today are also solving hard problems that are expensive and time-consuming for everyone to replicate.</p>
<p>Secondly, uniform interface are not necessarily semantically richer than &#8220;as generic as possible&#8221; interfaces or even &#8220;specialized&#8221; interfaces. For instance, a RESTful version of your example &#8220;BagOfBytes processThis(BagOfBytes)&#8221; would not provide all the semantics of the data and context for a client application to use it.</p>
<p>I have a longish comment at <a href="http://www.subbu.org/weblogs/main/2008/01/comments_on_ser.html" rel="nofollow">my blog</a>.</p>
<p>Subbu</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: subbu.org</title>
		<link>http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/comment-page-1/#comment-480</link>
		<dc:creator>subbu.org</dc:creator>
		<pubDate>Fri, 18 Jan 2008 18:17:57 +0000</pubDate>
		<guid isPermaLink="false">http://steve.vinoski.net/blog/2008/01/05/serendipitous-reuse/#comment-480</guid>
		<description>&lt;strong&gt;Comments on Serendipitous Reuse...&lt;/strong&gt;

I just finished reading an article in IEEE Computer titled &quot;Serendipitous Reuse&quot; (pdf here) by Steve Vinoski. There is also some interesting discussion on this article at Steve Vinoski&#039;s blog. The central premise of this article is that unif...</description>
		<content:encoded><![CDATA[<p><strong>Comments on Serendipitous Reuse&#8230;</strong></p>
<p>I just finished reading an article in IEEE Computer titled &quot;Serendipitous Reuse&quot; (pdf here) by Steve Vinoski. There is also some interesting discussion on this article at Steve Vinoski&#8217;s blog. The central premise of this article is that unif&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.175 seconds -->
