<?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"
	>
<channel>
	<title>Comments on: The value of a weakly typed Web Services interface</title>
	<atom:link href="http://undefined.com/ia/2006/12/05/the-value-of-a-weakly-typed-web-services-interface/feed/" rel="self" type="application/rss+xml" />
	<link>http://undefined.com/ia/2006/12/05/the-value-of-a-weakly-typed-web-services-interface/</link>
	<description>Agile &#38; Open Source Software, Economics, Liberty and Entrepreneurship</description>
	<pubDate>Fri, 29 Aug 2008 20:42:32 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: educhana</title>
		<link>http://undefined.com/ia/2006/12/05/the-value-of-a-weakly-typed-web-services-interface/#comment-2468</link>
		<dc:creator>educhana</dc:creator>
		<pubDate>Thu, 07 Dec 2006 09:19:59 +0000</pubDate>
		<guid isPermaLink="false">http://undefined.com/ia/2006/12/05/the-value-of-a-weakly-typed-web-services-interface/#comment-2468</guid>
		<description>Congratulations!

You have replicated the REST approach perfectly. Note that "put"--&#62;"POST"</description>
		<content:encoded><![CDATA[<p>Congratulations!</p>
<p>You have replicated the REST approach perfectly. Note that &#8220;put&#8221;&#8211;&gt;&#8221;POST&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jb</title>
		<link>http://undefined.com/ia/2006/12/05/the-value-of-a-weakly-typed-web-services-interface/#comment-2399</link>
		<dc:creator>jb</dc:creator>
		<pubDate>Wed, 06 Dec 2006 09:14:38 +0000</pubDate>
		<guid isPermaLink="false">http://undefined.com/ia/2006/12/05/the-value-of-a-weakly-typed-web-services-interface/#comment-2399</guid>
		<description>Well, I was trying to show that doing "getRealTimeStockQuote(â€œAAPLâ€, â€œ1.0â€) " was a bad idea.  For all the reasons you mention.

I guess I need to revisit the article and make that more clear.</description>
		<content:encoded><![CDATA[<p>Well, I was trying to show that doing &#8220;getRealTimeStockQuote(â€œAAPLâ€, â€œ1.0â€) &#8221; was a bad idea.  For all the reasons you mention.</p>
<p>I guess I need to revisit the article and make that more clear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Prashant Rane</title>
		<link>http://undefined.com/ia/2006/12/05/the-value-of-a-weakly-typed-web-services-interface/#comment-2393</link>
		<dc:creator>Prashant Rane</dc:creator>
		<pubDate>Wed, 06 Dec 2006 06:18:49 +0000</pubDate>
		<guid isPermaLink="false">http://undefined.com/ia/2006/12/05/the-value-of-a-weakly-typed-web-services-interface/#comment-2393</guid>
		<description>Are you serious about " getRealTimeStockQuote(â€œAAPLâ€, â€œ1.0â€)" part? Have you tried it yourself or are you just throwing it out as a possibility?

With that method same code handles all versions. Have you tried to add new version using this approach on .net or Axis stubs generated from WSDL? What if your schema evolves from 1.0 to 2.0? How do you specify two versions of same schema in a WSDL? 

With REST like approach you have different versions accessed via URL, handled by, possibly different code. No need to test and redeploy your existing service handlers they are fine on the existing URL.</description>
		<content:encoded><![CDATA[<p>Are you serious about &#8221; getRealTimeStockQuote(â€œAAPLâ€, â€œ1.0â€)&#8221; part? Have you tried it yourself or are you just throwing it out as a possibility?</p>
<p>With that method same code handles all versions. Have you tried to add new version using this approach on .net or Axis stubs generated from WSDL? What if your schema evolves from 1.0 to 2.0? How do you specify two versions of same schema in a WSDL? </p>
<p>With REST like approach you have different versions accessed via URL, handled by, possibly different code. No need to test and redeploy your existing service handlers they are fine on the existing URL.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
