<?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: REST is not so easy either</title>
	<atom:link href="http://www.a-chinaman.com/2005/10/13/rest-is-not-so-easy-either/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.a-chinaman.com/2005/10/13/rest-is-not-so-easy-either/</link>
	<description>一個中國人, 這是我的故事</description>
	<pubDate>Fri, 21 Nov 2008 18:33:08 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Chui Tey</title>
		<link>http://www.a-chinaman.com/2005/10/13/rest-is-not-so-easy-either/#comment-280</link>
		<dc:creator>Chui Tey</dc:creator>
		<pubDate>Mon, 24 Oct 2005 09:45:50 +0000</pubDate>
		<guid isPermaLink="false">http://64.22.124.146/wordpress/?p=67#comment-280</guid>
		<description>One of the implicit assumptions behind a REST API is that the document is the interface.  The Ruby API is just one interpretation of the document structure.

I volunteer that the problems you encountered is a vindication of a doc-literal approach as opposed to the RPC-wrapper that WSDL generates.

Integration is hard, especially since you are dealing with unfamiliar semantics. Rip up all the layers of indirection caused by the wrappers and you end up with a nice transparent description of the service.</description>
		<content:encoded><![CDATA[<p>One of the implicit assumptions behind a REST API is that the document is the interface.  The Ruby API is just one interpretation of the document structure.</p>
<p>I volunteer that the problems you encountered is a vindication of a doc-literal approach as opposed to the RPC-wrapper that WSDL generates.</p>
<p>Integration is hard, especially since you are dealing with unfamiliar semantics. Rip up all the layers of indirection caused by the wrappers and you end up with a nice transparent description of the service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: HMM</title>
		<link>http://www.a-chinaman.com/2005/10/13/rest-is-not-so-easy-either/#comment-279</link>
		<dc:creator>HMM</dc:creator>
		<pubDate>Thu, 13 Oct 2005 16:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://64.22.124.146/wordpress/?p=67#comment-279</guid>
		<description>Just because you couldn't install RubyGems or that you found a bug in the Ruby implementation you got doesn't mean REST is hard.
In fact, that's the single most stupid argument I've ever heard against REST and pro SOAP and that just to advertise ASP.NET Web Services (or better yet, Indigo).
Stop spreading FUD and get a life.</description>
		<content:encoded><![CDATA[<p>Just because you couldn&#8217;t install RubyGems or that you found a bug in the Ruby implementation you got doesn&#8217;t mean REST is hard.<br />
In fact, that&#8217;s the single most stupid argument I&#8217;ve ever heard against REST and pro SOAP and that just to advertise ASP.NET Web Services (or better yet, Indigo).<br />
Stop spreading FUD and get a life.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roy Tate</title>
		<link>http://www.a-chinaman.com/2005/10/13/rest-is-not-so-easy-either/#comment-278</link>
		<dc:creator>Roy Tate</dc:creator>
		<pubDate>Thu, 13 Oct 2005 15:14:36 +0000</pubDate>
		<guid isPermaLink="false">http://64.22.124.146/wordpress/?p=67#comment-278</guid>
		<description>I only installed Ruby and Gem via APT-GET, then used Gem for Rake, Rails, etc.  It is easy, and I can get anything I want on RubyForge.  If I used APT-GET, I would still have to download and install all of the packages that Ubuntu/Debian don't cover.</description>
		<content:encoded><![CDATA[<p>I only installed Ruby and Gem via APT-GET, then used Gem for Rake, Rails, etc.  It is easy, and I can get anything I want on RubyForge.  If I used APT-GET, I would still have to download and install all of the packages that Ubuntu/Debian don&#8217;t cover.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AC</title>
		<link>http://www.a-chinaman.com/2005/10/13/rest-is-not-so-easy-either/#comment-277</link>
		<dc:creator>AC</dc:creator>
		<pubDate>Thu, 13 Oct 2005 14:30:40 +0000</pubDate>
		<guid isPermaLink="false">http://64.22.124.146/wordpress/?p=67#comment-277</guid>
		<description>Well if you aren't too annoyed to want to continue you might check into &lt;a href="http://phpFlickr.com" rel="nofollow"&gt;phpFlickr&lt;/a&gt; or one of the tools based on it. It even has a wordpress specific plugin last I knew.</description>
		<content:encoded><![CDATA[<p>Well if you aren&#8217;t too annoyed to want to continue you might check into <a href="http://phpFlickr.com" rel="nofollow">phpFlickr</a> or one of the tools based on it. It even has a wordpress specific plugin last I knew.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay R. Wren</title>
		<link>http://www.a-chinaman.com/2005/10/13/rest-is-not-so-easy-either/#comment-276</link>
		<dc:creator>Jay R. Wren</dc:creator>
		<pubDate>Thu, 13 Oct 2005 13:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://64.22.124.146/wordpress/?p=67#comment-276</guid>
		<description>I can relate to your frustration on two points.  I also recently tried ruby development on Ubuntu.  As soon as I needed a Gem I gave up, I'm glad you went a step further and did the source, maybe I'll do that next time.

I've done some flickr development.  I found the perl API to be very easy to use.  Of course perl is a horrible language compared to python, ruby, or smalltalk, but it really was not difficult.  The hardest part was finding how to access what I wanted.  The perl api just read the xml response into a hash with node names as keys.  Useing a perl debugger is not fun.

Good luck.  Maybe we could team up to start packaging some of those ruby modules for Ubuntu/Debian.</description>
		<content:encoded><![CDATA[<p>I can relate to your frustration on two points.  I also recently tried ruby development on Ubuntu.  As soon as I needed a Gem I gave up, I&#8217;m glad you went a step further and did the source, maybe I&#8217;ll do that next time.</p>
<p>I&#8217;ve done some flickr development.  I found the perl API to be very easy to use.  Of course perl is a horrible language compared to python, ruby, or smalltalk, but it really was not difficult.  The hardest part was finding how to access what I wanted.  The perl api just read the xml response into a hash with node names as keys.  Useing a perl debugger is not fun.</p>
<p>Good luck.  Maybe we could team up to start packaging some of those ruby modules for Ubuntu/Debian.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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