<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: PayPal&#8217;s New API: So Close, Yet So Far</title>
	<link>http://blog.welldesignedurls.org/2007/02/16/paypals-new-name-value-pair-api/</link>
	<description>Advocating User-Centered URL Design</description>
	<pubDate>Thu, 09 Sep 2010 00:57:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.2</generator>

	<item>
		<title>By: Dinakar</title>
		<link>http://blog.welldesignedurls.org/2007/02/16/paypals-new-name-value-pair-api/#comment-124807</link>
		<author>Dinakar</author>
		<pubDate>Fri, 17 Apr 2009 14:38:51 +0000</pubDate>
		<guid>http://blog.welldesignedurls.org/2007/02/16/paypals-new-name-value-pair-api/#comment-124807</guid>
					<description>I am using NVP over SOAP for my website. my manager says SOAP is better because in NVP, if the server goes down, it will be a problem. But, isnt it a problem either way? if the server goes down, the webservice (i.e., even using SOAP API) also goes down with it ....am I correct?</description>
		<content:encoded><![CDATA[<p>I am using NVP over SOAP for my website. my manager says SOAP is better because in NVP, if the server goes down, it will be a problem. But, isnt it a problem either way? if the server goes down, the webservice (i.e., even using SOAP API) also goes down with it &#8230;.am I correct?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Mike Schinkel</title>
		<link>http://blog.welldesignedurls.org/2007/02/16/paypals-new-name-value-pair-api/#comment-124814</link>
		<author>Mike Schinkel</author>
		<pubDate>Fri, 17 Apr 2009 18:48:49 +0000</pubDate>
		<guid>http://blog.welldesignedurls.org/2007/02/16/paypals-new-name-value-pair-api/#comment-124814</guid>
					<description>As far as I'm concerned SOAP is a complete nightmare and yes, you are correct if the server goes down it's the same problem. That is unless you use SOAP over store-and-forward mechanisms (like SMTP) instead of over HTTP but then what you are doing is a completely different type of web service.

Let me repeat, SOAP is a nightmare.  RESTful web services are the way to go. If you need high-availability, use Amazon EC2 or something similar.</description>
		<content:encoded><![CDATA[<p>As far as I&#8217;m concerned SOAP is a complete nightmare and yes, you are correct if the server goes down it&#8217;s the same problem. That is unless you use SOAP over store-and-forward mechanisms (like SMTP) instead of over HTTP but then what you are doing is a completely different type of web service.</p>
<p>Let me repeat, SOAP is a nightmare.  RESTful web services are the way to go. If you need high-availability, use Amazon EC2 or something similar.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
