<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The rest of the soap</title>
	<link>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/</link>
	<description>Genealogy anywhere.</description>
	<pubDate>Fri, 05 Sep 2008 20:57:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: Richard K Miller</title>
		<link>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-158</link>
		<pubDate>Tue, 16 May 2006 06:48:29 +0000</pubDate>
		<guid>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-158</guid>
					<description>REST is easier to use since you can test queries in your browser and you don't usually need any special libraries to access REST services.

SOAP is more complicated.  In PHP it requires PHP 5 or the NuSOAP library.  But once I got it, after a steeper learning curve, it seemed more magical.

Yahoo uses REST in (almost?) all of its web services.  I particularly like that you can append &quot;&amp;#38;output=php&quot; and it will return a string of character that you can unserialize() into an array.  It makes it almost like SOAP but much much easier.</description>
		<content:encoded><![CDATA[<p>REST is easier to use since you can test queries in your browser and you don&#8217;t usually need any special libraries to access REST services.</p>
<p>SOAP is more complicated.  In PHP it requires PHP 5 or the NuSOAP library.  But once I got it, after a steeper learning curve, it seemed more magical.</p>
<p>Yahoo uses REST in (almost?) all of its web services.  I particularly like that you can append &#8220;&amp;output=php&#8221; and it will return a string of character that you can unserialize() into an array.  It makes it almost like SOAP but much much easier.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Logan Allred</title>
		<link>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-156</link>
		<pubDate>Sun, 14 May 2006 15:11:53 +0000</pubDate>
		<guid>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-156</guid>
					<description>I found some links:

http://www.theserverside.com/talks/index.tss (Ted Neward, down the page a little)

http://www.intertwingly.net/stories/2002/07/20/restSoap.html

I also have slides from a presentation I attended by Ted Neward where he goes more in depth. I'll shoot those to you in email once I find them.</description>
		<content:encoded><![CDATA[<p>I found some links:</p>
<p><a href='http://www.theserverside.com/talks/index.tss' rel='nofollow'>http://www.theserverside.com/talks/index.tss</a> (Ted Neward, down the page a little)</p>
<p><a href='http://www.intertwingly.net/stories/2002/07/20/restSoap.html' rel='nofollow'>http://www.intertwingly.net/stories/2002/07/20/restSoap.html</a></p>
<p>I also have slides from a presentation I attended by Ted Neward where he goes more in depth. I&#8217;ll shoot those to you in email once I find them.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ben</title>
		<link>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-154</link>
		<pubDate>Sat, 13 May 2006 15:27:29 +0000</pubDate>
		<guid>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-154</guid>
					<description>The place I think I got the idea that RoR is more SOAPy was &lt;a href=&quot;http://en.wikipedia.org/wiki/Ruby_on_rails&quot; rel=&quot;nofollow&quot;&gt;Wikipedia&lt;/a&gt;:

&lt;blockquote&gt;
In addition to this, Rails also offers some other modules, like Action Mailer for sending email and Action Web Service for SOAP and XML-RPC support.
&lt;/blockquote&gt;

Regardless, I really like that idea of wrapping the REST service in a SOAP envelope.  I wonder if Flickr does that...  If you do find a link (I couldn't find one either), let me know.</description>
		<content:encoded><![CDATA[<p>The place I think I got the idea that RoR is more SOAPy was <a href="http://en.wikipedia.org/wiki/Ruby_on_rails" rel="nofollow">Wikipedia</a>:</p>
<blockquote><p>
In addition to this, Rails also offers some other modules, like Action Mailer for sending email and Action Web Service for SOAP and XML-RPC support.
</p></blockquote>
<p>Regardless, I really like that idea of wrapping the REST service in a SOAP envelope.  I wonder if Flickr does that&#8230;  If you do find a link (I couldn&#8217;t find one either), let me know.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Logan Allred</title>
		<link>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-153</link>
		<pubDate>Sat, 13 May 2006 15:04:22 +0000</pubDate>
		<guid>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-153</guid>
					<description>Just to clarify, I should've send SOAP envelope instead of SOAP header.</description>
		<content:encoded><![CDATA[<p>Just to clarify, I should&#8217;ve send SOAP envelope instead of SOAP header.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Logan Allred</title>
		<link>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-152</link>
		<pubDate>Sat, 13 May 2006 14:56:13 +0000</pubDate>
		<guid>http://www.beyondproject.org/2006/05/12/the-rest-of-the-soap/#comment-152</guid>
					<description>Interesting, I always got the impression that Ruby on Rails was very much focused on REST. I really haven't looked at their web services, so maybe I'm confusing their RESTful web preferences with their web service structure.

Anyway, I've always liked Ted Newards somewhat pragmatic approach to this. I can't find a working link right now, but his basic point is to take your REST services and wrap them in a SOAP header. It's easy for non-SOAP folks to just unwrap the header and grab the content, and SOAP folks can just consume it. I've never tried it in practice, but it sounds feasible.</description>
		<content:encoded><![CDATA[<p>Interesting, I always got the impression that Ruby on Rails was very much focused on REST. I really haven&#8217;t looked at their web services, so maybe I&#8217;m confusing their RESTful web preferences with their web service structure.</p>
<p>Anyway, I&#8217;ve always liked Ted Newards somewhat pragmatic approach to this. I can&#8217;t find a working link right now, but his basic point is to take your REST services and wrap them in a SOAP header. It&#8217;s easy for non-SOAP folks to just unwrap the header and grab the content, and SOAP folks can just consume it. I&#8217;ve never tried it in practice, but it sounds feasible.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
