<?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: Using WCF for REST, Part 2</title>
	<atom:link href="http://underground.infovark.com/2008/05/17/using-wcf-for-rest-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://underground.infovark.com/2008/05/17/using-wcf-for-rest-part-2/</link>
	<description>The Infovark technology blog</description>
	<lastBuildDate>Fri, 19 Feb 2010 02:24:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rinsing the SOAP from WCF (or, RESTful WCF Hyperlink Acupuncture) &#124; The Freak Parade</title>
		<link>http://underground.infovark.com/2008/05/17/using-wcf-for-rest-part-2/comment-page-1/#comment-74</link>
		<dc:creator>Rinsing the SOAP from WCF (or, RESTful WCF Hyperlink Acupuncture) &#124; The Freak Parade</dc:creator>
		<pubDate>Thu, 28 Aug 2008 22:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://underground.infovark.com/?p=21#comment-74</guid>
		<description>[...] WCF for REST, Part 1, Part2 and Part 3. Make sure you read all the comments though, several of the gripes brought up in these [...]</description>
		<content:encoded><![CDATA[<p>[...] WCF for REST, Part 1, Part2 and Part 3. Make sure you read all the comments though, several of the gripes brought up in these [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Using WCF for REST, Part 3 &#171; Infovark Underground</title>
		<link>http://underground.infovark.com/2008/05/17/using-wcf-for-rest-part-2/comment-page-1/#comment-29</link>
		<dc:creator>Using WCF for REST, Part 3 &#171; Infovark Underground</dc:creator>
		<pubDate>Tue, 27 May 2008 15:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://underground.infovark.com/?p=21#comment-29</guid>
		<description>[...] easiest way to explain the issues we encountered when implementing REST is to work through the design principles we followed. I think much of our trouble came from the [...]</description>
		<content:encoded><![CDATA[<p>[...] easiest way to explain the issues we encountered when implementing REST is to work through the design principles we followed. I think much of our trouble came from the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean</title>
		<link>http://underground.infovark.com/2008/05/17/using-wcf-for-rest-part-2/comment-page-1/#comment-25</link>
		<dc:creator>Dean</dc:creator>
		<pubDate>Wed, 21 May 2008 22:52:04 +0000</pubDate>
		<guid isPermaLink="false">http://underground.infovark.com/?p=21#comment-25</guid>
		<description>Hey Steve, glad you stopped by. I&#039;ve found &lt;a href=&quot;hyperthink.net/blog&quot; rel=&quot;nofollow&quot;&gt;Brain.Save()&lt;/a&gt; very useful for getting a handle on this WCF stuff.

I started writing an explanation of #4, but it was too long for a comment. I&#039;ll get a post up soon about our REST design.</description>
		<content:encoded><![CDATA[<p>Hey Steve, glad you stopped by. I&#8217;ve found <a href="hyperthink.net/blog" rel="nofollow">Brain.Save()</a> very useful for getting a handle on this WCF stuff.</p>
<p>I started writing an explanation of #4, but it was too long for a comment. I&#8217;ll get a post up soon about our REST design.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Maine</title>
		<link>http://underground.infovark.com/2008/05/17/using-wcf-for-rest-part-2/comment-page-1/#comment-22</link>
		<dc:creator>Steve Maine</dc:creator>
		<pubDate>Sun, 18 May 2008 05:16:22 +0000</pubDate>
		<guid isPermaLink="false">http://underground.infovark.com/?p=21#comment-22</guid>
		<description>Thanks for posting this! I&#039;m looking forward to reading more about your experiences as they all sound like good issues.

I&#039;m interested in all of them, but (4) is the one that piques my curiosity the most. What kind of factoring patterns would you like to be able to do, but can&#039;t? To what degree does the single-implementation-type-per-service restriction play in here?
-smaine</description>
		<content:encoded><![CDATA[<p>Thanks for posting this! I&#8217;m looking forward to reading more about your experiences as they all sound like good issues.</p>
<p>I&#8217;m interested in all of them, but (4) is the one that piques my curiosity the most. What kind of factoring patterns would you like to be able to do, but can&#8217;t? To what degree does the single-implementation-type-per-service restriction play in here?<br />
-smaine</p>
]]></content:encoded>
	</item>
</channel>
</rss>
