<?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: Thoughts around REST</title>
	<atom:link href="http://tech.poglianis.net/2007/03/08/thoughts-around-rest/feed/" rel="self" type="application/rss+xml" />
	<link>http://tech.poglianis.net/2007/03/08/thoughts-around-rest/</link>
	<description>Opinions... because I choose. Always !</description>
	<lastBuildDate>Tue, 13 Jul 2010 21:43:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Stefano Pogliani</title>
		<link>http://tech.poglianis.net/2007/03/08/thoughts-around-rest/comment-page-1/#comment-5012</link>
		<dc:creator>Stefano Pogliani</dc:creator>
		<pubDate>Sun, 07 Mar 2010 22:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://tech.poglianis.net/2007/03/08/thoughts-around-rest/#comment-5012</guid>
		<description>JJ
 I am not sure I would go that far.
What I, on the contrary, think is that our industry lost a great opportunity. The opportunity to develop something different from the HTML/Javascript in order to support the new generation of applications delivered over the web.</description>
		<content:encoded><![CDATA[<p>JJ<br />
 I am not sure I would go that far.<br />
What I, on the contrary, think is that our industry lost a great opportunity. The opportunity to develop something different from the HTML/Javascript in order to support the new generation of applications delivered over the web.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean-Jacques Dubray</title>
		<link>http://tech.poglianis.net/2007/03/08/thoughts-around-rest/comment-page-1/#comment-5010</link>
		<dc:creator>Jean-Jacques Dubray</dc:creator>
		<pubDate>Sun, 07 Mar 2010 00:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://tech.poglianis.net/2007/03/08/thoughts-around-rest/#comment-5010</guid>
		<description>Assaf:

when will you finally understand something about SOA and BPM? Distributed computing is not about some piece of code having the ability to call some other piece of code. It is not about distributed objects vs static methods. Distributing objects has been tried countless times. That will never work. The problem is the semantics of monolithic synchronous runtimes such as OO. Trying to make a distributed call local is the problem, not the solution. Yet, you and so many other always come back there. 

You need to create a distributed programming model from scratch, independent of the runtime in which some of the components are implemented. You will actually then understand the need for bi-directional interfaces, orchestration languages, forwards versioning and assemblies. Maybe, just maybe the &quot;unit of assembly&quot; may not the &quot;object&quot;, maybe, just maybe, it could be something else? don&#039;t you think we tried enough times? What&#039;s important is to be able to &quot;assemble&quot; software components that were built by different people at different time using different technologies. It does not matter if it is an object, a static method or a service component? 

Stephano:

thank you for having the courage to not be a &quot;follower&quot; of the &quot;good thinkers&quot; of our industry. 

JJ-</description>
		<content:encoded><![CDATA[<p>Assaf:</p>
<p>when will you finally understand something about SOA and BPM? Distributed computing is not about some piece of code having the ability to call some other piece of code. It is not about distributed objects vs static methods. Distributing objects has been tried countless times. That will never work. The problem is the semantics of monolithic synchronous runtimes such as OO. Trying to make a distributed call local is the problem, not the solution. Yet, you and so many other always come back there. </p>
<p>You need to create a distributed programming model from scratch, independent of the runtime in which some of the components are implemented. You will actually then understand the need for bi-directional interfaces, orchestration languages, forwards versioning and assemblies. Maybe, just maybe the &#8220;unit of assembly&#8221; may not the &#8220;object&#8221;, maybe, just maybe, it could be something else? don&#8217;t you think we tried enough times? What&#8217;s important is to be able to &#8220;assemble&#8221; software components that were built by different people at different time using different technologies. It does not matter if it is an object, a static method or a service component? </p>
<p>Stephano:</p>
<p>thank you for having the courage to not be a &#8220;follower&#8221; of the &#8220;good thinkers&#8221; of our industry. </p>
<p>JJ-</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: assaf</title>
		<link>http://tech.poglianis.net/2007/03/08/thoughts-around-rest/comment-page-1/#comment-3332</link>
		<dc:creator>assaf</dc:creator>
		<pubDate>Thu, 08 Mar 2007 17:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://tech.poglianis.net/2007/03/08/thoughts-around-rest/#comment-3332</guid>
		<description>A good analogy for REST is calling an object, getting back a reference to another object, calling that object, getting back a reference, and so forth.

A good analogy for SOAP is only ever calling static methods, and passing arguments around to tell the static method which instance you actually ment to call, if you could.

So I&#039;m confused when you say REST is the counter intuitive one.</description>
		<content:encoded><![CDATA[<p>A good analogy for REST is calling an object, getting back a reference to another object, calling that object, getting back a reference, and so forth.</p>
<p>A good analogy for SOAP is only ever calling static methods, and passing arguments around to tell the static method which instance you actually ment to call, if you could.</p>
<p>So I&#8217;m confused when you say REST is the counter intuitive one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
