<?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: OpenRasta &#8211; a really ReSTful alternative to WCF</title>
	<atom:link href="http://www.zephyros-systems.co.uk/blog/index.php?feed=rss2&#038;p=45" rel="self" type="application/rss+xml" />
	<link>http://www.zephyros-systems.co.uk/blog/?p=45</link>
	<description>A decade of Delphi, a little less .NET</description>
	<lastBuildDate>Tue, 26 Jan 2010 13:25:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: uberVU - social comments</title>
		<link>http://www.zephyros-systems.co.uk/blog/?p=45&#038;cpage=1#comment-36951</link>
		<dc:creator>uberVU - social comments</dc:creator>
		<pubDate>Tue, 26 Jan 2010 13:25:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.zephyros-systems.co.uk/blog/?p=45#comment-36951</guid>
		<description>&lt;strong&gt;Social comments and analytics for this post...&lt;/strong&gt;

This post was mentioned on Twitter by andybritcliffe: Great blog pitting WCF v OpenRasta or more accurately why you should use OpenRasta over WCF if you want REST services http://bit.ly/5epLfy...</description>
		<content:encoded><![CDATA[<p><strong>Social comments and analytics for this post&#8230;</strong></p>
<p>This post was mentioned on Twitter by andybritcliffe: Great blog pitting WCF v OpenRasta or more accurately why you should use OpenRasta over WCF if you want REST services <a href="http://bit.ly/5epLfy..." rel="nofollow">http://bit.ly/5epLfy&#8230;</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://www.zephyros-systems.co.uk/blog/?p=45&#038;cpage=1#comment-36950</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Tue, 26 Jan 2010 13:21:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.zephyros-systems.co.uk/blog/?p=45#comment-36950</guid>
		<description>Hi Jesse, thanks for the feedback. I&#039;m not comparing REST to WCF.  I&#039;m comparing two implementations that claim support for ReST as an architectural style. One library has been built ground-up to support only ReST; the other has been built to try to support more or less anything, and as a result, compromises ReST in areas which were key for us.

Don&#039;t get me wrong, I like WCF a lot for certain types of application (basically, service orientation);  I simply feel that people will see WCF and its ReST starter kit and think &quot;right, this is the way to do ReST - with WCF&quot; when &lt;strong&gt;out of the box&lt;/strong&gt; WCF is very biased towards RPC, which ReST isn&#039;t.  You said it yourself - WCF is massively configurable and could be made to be more ReST-idiomatic, but that&#039;s an awful lot of work, especially for people who aren&#039;t 100% familiar with the complex WCF extensibility story (I&#039;m guessing you are - some good content on your site that I&#039;m about to spend a bit of time reading ;)). OpenRasta has not only done this work already, it&#039;s also baked in IoC at the framework level to make TDD-ed handlers trivial.  I was really struggling to test WCF ReST services except at integration level.

I think WCF was just a bit too flexible for its own good as far as we were concerned.  It requires that you turn up with all your opinions fully-formed and implement parts of the framework yourself to fit your opinions (which I&#039;m not sure we had!).  OpenRasta arrives with its opinions on its sleeve and forces you into good ReST practice (even if you don&#039;t know it yet!).  Those constraints turned out to be incredibly liberating for us and made us concentrate on what we were delivering rather than how to deliver it.</description>
		<content:encoded><![CDATA[<p>Hi Jesse, thanks for the feedback. I&#8217;m not comparing REST to WCF.  I&#8217;m comparing two implementations that claim support for ReST as an architectural style. One library has been built ground-up to support only ReST; the other has been built to try to support more or less anything, and as a result, compromises ReST in areas which were key for us.</p>
<p>Don&#8217;t get me wrong, I like WCF a lot for certain types of application (basically, service orientation);  I simply feel that people will see WCF and its ReST starter kit and think &#8220;right, this is the way to do ReST &#8211; with WCF&#8221; when <strong>out of the box</strong> WCF is very biased towards RPC, which ReST isn&#8217;t.  You said it yourself &#8211; WCF is massively configurable and could be made to be more ReST-idiomatic, but that&#8217;s an awful lot of work, especially for people who aren&#8217;t 100% familiar with the complex WCF extensibility story (I&#8217;m guessing you are &#8211; some good content on your site that I&#8217;m about to spend a bit of time reading <img src='http://www.zephyros-systems.co.uk/blog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> ). OpenRasta has not only done this work already, it&#8217;s also baked in IoC at the framework level to make TDD-ed handlers trivial.  I was really struggling to test WCF ReST services except at integration level.</p>
<p>I think WCF was just a bit too flexible for its own good as far as we were concerned.  It requires that you turn up with all your opinions fully-formed and implement parts of the framework yourself to fit your opinions (which I&#8217;m not sure we had!).  OpenRasta arrives with its opinions on its sleeve and forces you into good ReST practice (even if you don&#8217;t know it yet!).  Those constraints turned out to be incredibly liberating for us and made us concentrate on what we were delivering rather than how to deliver it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Ezell</title>
		<link>http://www.zephyros-systems.co.uk/blog/?p=45&#038;cpage=1#comment-36948</link>
		<dc:creator>Jesse Ezell</dc:creator>
		<pubDate>Tue, 26 Jan 2010 10:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.zephyros-systems.co.uk/blog/?p=45#comment-36948</guid>
		<description>OpenRasta is a great project, and I respect Seb&#039;s knowledge of REST better than just about anyone I know. However, comparing REST and WCF isn&#039;t really a good comparison since REST is an architectural style and WCF is a library.

WCF can actually be customized to do all sorts of things at the transport layer and work with raw messages to support all the same scenarios... unfortunately, there hasn&#039;t been too much work done in that area, but it certainly is possible.

Here&#039;s some of the basics:

http://blog.iserviceoriented.com/index.php/2010/01/23/building-a-basic-web-server-using-wcf/

A little more complicated than using HttpListeners... but much more powerful in the right hands.

In any case, OpenRasta is a great framework, so don&#039;t want to detract at all from it, but there is a lot more to WCF than many people realize.</description>
		<content:encoded><![CDATA[<p>OpenRasta is a great project, and I respect Seb&#8217;s knowledge of REST better than just about anyone I know. However, comparing REST and WCF isn&#8217;t really a good comparison since REST is an architectural style and WCF is a library.</p>
<p>WCF can actually be customized to do all sorts of things at the transport layer and work with raw messages to support all the same scenarios&#8230; unfortunately, there hasn&#8217;t been too much work done in that area, but it certainly is possible.</p>
<p>Here&#8217;s some of the basics:</p>
<p><a href="http://blog.iserviceoriented.com/index.php/2010/01/23/building-a-basic-web-server-using-wcf/" rel="nofollow">http://blog.iserviceoriented.com/index.php/2010/01/23/building-a-basic-web-server-using-wcf/</a></p>
<p>A little more complicated than using HttpListeners&#8230; but much more powerful in the right hands.</p>
<p>In any case, OpenRasta is a great framework, so don&#8217;t want to detract at all from it, but there is a lot more to WCF than many people realize.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
