<?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 for Paul Donnelly</title>
	<atom:link href="http://paul.donnelly.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://paul.donnelly.org</link>
	<description>my personal blog and netstream</description>
	<lastBuildDate>Wed, 20 Apr 2011 23:57:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Comment on 2-legged OAuth Javascript Function for YQL by bcmoney</title>
		<link>http://paul.donnelly.org/2008/10/31/2-legged-oauth-javascript-function-for-yql/comment-page-1/#comment-97</link>
		<dc:creator>bcmoney</dc:creator>
		<pubDate>Wed, 20 Apr 2011 23:57:37 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=36#comment-97</guid>
		<description>This is really the single most excellent OAuth and YQL tutorial I have ever read. I have used it on more than a couple occasions to prove to unbelieving managers or fellow developers that the OAuth authorization flow was possible in pure client-side JavaScript (mind you there&#039;s a need to store some key information publicly). 

As of today though, I noticed it no longer works. This may be related to the fact that OAuth 2.0 requires HTTPS (SSL) support in any libraries for the new request signing and protection process (presumably to disallow storing keys in plain view in the client). 

Do you happen to know if it is possible to ever get this working again, or is the JavaScript OAuth library history, like much of Yahoo!&#039;s original Search and Information Retrieval Web Services?

If you have any ideas on how to get this working again I would be most grateful, and CHEERS for the initial effort on the OAuth 1.0 version!</description>
		<content:encoded><![CDATA[<p>This is really the single most excellent OAuth and YQL tutorial I have ever read. I have used it on more than a couple occasions to prove to unbelieving managers or fellow developers that the OAuth authorization flow was possible in pure client-side JavaScript (mind you there&#8217;s a need to store some key information publicly). </p>
<p>As of today though, I noticed it no longer works. This may be related to the fact that OAuth 2.0 requires HTTPS (SSL) support in any libraries for the new request signing and protection process (presumably to disallow storing keys in plain view in the client). </p>
<p>Do you happen to know if it is possible to ever get this working again, or is the JavaScript OAuth library history, like much of Yahoo!&#8217;s original Search and Information Retrieval Web Services?</p>
<p>If you have any ideas on how to get this working again I would be most grateful, and CHEERS for the initial effort on the OAuth 1.0 version!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2-legged OAuth Javascript Function for YQL by George</title>
		<link>http://paul.donnelly.org/2008/10/31/2-legged-oauth-javascript-function-for-yql/comment-page-1/#comment-76</link>
		<dc:creator>George</dc:creator>
		<pubDate>Wed, 30 Jun 2010 18:01:36 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=36#comment-76</guid>
		<description>Hello there,
That&#039;s a really goog article.

I have a question on how to use this script to obtain a signed query but retieving the source code of the specified url. I tried changing the query with the appropriate one  in the sample app but i can&#039;t find any solution to retrieve the responded source code of the queried. 

Any help on this would really appreciate it!

Thank you very much

Regards,
George</description>
		<content:encoded><![CDATA[<p>Hello there,<br />
That&#8217;s a really goog article.</p>
<p>I have a question on how to use this script to obtain a signed query but retieving the source code of the specified url. I tried changing the query with the appropriate one  in the sample app but i can&#8217;t find any solution to retrieve the responded source code of the queried. </p>
<p>Any help on this would really appreciate it!</p>
<p>Thank you very much</p>
<p>Regards,<br />
George</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2-legged OAuth Javascript Function for YQL by James Wragg</title>
		<link>http://paul.donnelly.org/2008/10/31/2-legged-oauth-javascript-function-for-yql/comment-page-1/#comment-72</link>
		<dc:creator>James Wragg</dc:creator>
		<pubDate>Thu, 18 Mar 2010 16:28:03 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=36#comment-72</guid>
		<description>Actually, make that encodeURIComponent()



&lt;blockquote&gt;**changed code in blog to reflect&lt;/blockquote&gt;

</description>
		<content:encoded><![CDATA[<p>Actually, make that encodeURIComponent()</p>
<blockquote><p>**changed code in blog to reflect</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2-legged OAuth Javascript Function for YQL by James Wragg</title>
		<link>http://paul.donnelly.org/2008/10/31/2-legged-oauth-javascript-function-for-yql/comment-page-1/#comment-71</link>
		<dc:creator>James Wragg</dc:creator>
		<pubDate>Thu, 18 Mar 2010 16:15:50 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=36#comment-71</guid>
		<description>Note for anyone looking to use this function: You need to correctly encode the signature, otherwise plus (+) chars are ignored as spaces:
paramList.push(&quot;oauth_signature=&quot;+encodeURI(theSig));


&lt;blockquote&gt;**changed code in blog to reflect&lt;/blockquote&gt;


</description>
		<content:encoded><![CDATA[<p>Note for anyone looking to use this function: You need to correctly encode the signature, otherwise plus (+) chars are ignored as spaces:<br />
paramList.push(&#8220;oauth_signature=&#8221;+encodeURI(theSig));</p>
<blockquote><p>**changed code in blog to reflect</p></blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2-legged OAuth Javascript Function for YQL by Pete</title>
		<link>http://paul.donnelly.org/2008/10/31/2-legged-oauth-javascript-function-for-yql/comment-page-1/#comment-56</link>
		<dc:creator>Pete</dc:creator>
		<pubDate>Wed, 19 Aug 2009 16:04:20 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=36#comment-56</guid>
		<description>Paul,

I&#039;ve stolen your code and made it into a little twitter page.

http://www.infonote.com/yqltweet.htm

It&#039;s helped me a lot to understand the Oauth requirements, many thanks.</description>
		<content:encoded><![CDATA[<p>Paul,</p>
<p>I&#8217;ve stolen your code and made it into a little twitter page.</p>
<p><a href="http://www.infonote.com/yqltweet.htm" rel="nofollow">http://www.infonote.com/yqltweet.htm</a></p>
<p>It&#8217;s helped me a lot to understand the Oauth requirements, many thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 2-legged OAuth Javascript Function for YQL by Katya</title>
		<link>http://paul.donnelly.org/2008/10/31/2-legged-oauth-javascript-function-for-yql/comment-page-1/#comment-41</link>
		<dc:creator>Katya</dc:creator>
		<pubDate>Thu, 16 Jul 2009 00:40:45 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=36#comment-41</guid>
		<description>Thanks for posting this. It helped a lot!</description>
		<content:encoded><![CDATA[<p>Thanks for posting this. It helped a lot!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on YQL and JSONP-X (aka. json-p-x, jsonpx, json-px) by Chris Heilmann</title>
		<link>http://paul.donnelly.org/2009/07/08/yql-and-jsonp-x/comment-page-1/#comment-22</link>
		<dc:creator>Chris Heilmann</dc:creator>
		<pubDate>Fri, 10 Jul 2009 08:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=96#comment-22</guid>
		<description>Great stuff, will cross-link it from my posts on the matter.</description>
		<content:encoded><![CDATA[<p>Great stuff, will cross-link it from my posts on the matter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on YQL and JSONP-X (aka. json-p-x, jsonpx, json-px) by Paul Donnelly</title>
		<link>http://paul.donnelly.org/2009/07/08/yql-and-jsonp-x/comment-page-1/#comment-21</link>
		<dc:creator>Paul Donnelly</dc:creator>
		<pubDate>Fri, 10 Jul 2009 06:17:28 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=96#comment-21</guid>
		<description>@Ryan, the main advantage is that you don&#039;t have to loop through your JSON result to construct HTML - not that its hard to do, but just cuts out another step. Also HTML to JSON is some what lossy (read: http://developer.yahoo.net/forum/index.php?showtopic=649). Using JSONP-X keeps the HTML structure you want entirely intact when using this type of JSON payload.</description>
		<content:encoded><![CDATA[<p>@Ryan, the main advantage is that you don&#8217;t have to loop through your JSON result to construct HTML &#8211; not that its hard to do, but just cuts out another step. Also HTML to JSON is some what lossy (read: <a href="http://developer.yahoo.net/forum/index.php?showtopic=649)" rel="nofollow">http://developer.yahoo.net/forum/index.php?showtopic=649)</a>. Using JSONP-X keeps the HTML structure you want entirely intact when using this type of JSON payload.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on YQL and JSONP-X (aka. json-p-x, jsonpx, json-px) by Ryan</title>
		<link>http://paul.donnelly.org/2009/07/08/yql-and-jsonp-x/comment-page-1/#comment-20</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Fri, 10 Jul 2009 05:23:58 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=96#comment-20</guid>
		<description>Great work, I have been using format=json&amp;callback=callback on my YQL query for sometime now what advantage does this new way have?</description>
		<content:encoded><![CDATA[<p>Great work, I have been using format=json&amp;callback=callback on my YQL query for sometime now what advantage does this new way have?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on YQL and JSONP-X (aka. json-p-x, jsonpx, json-px) by russell</title>
		<link>http://paul.donnelly.org/2009/07/08/yql-and-jsonp-x/comment-page-1/#comment-19</link>
		<dc:creator>russell</dc:creator>
		<pubDate>Thu, 09 Jul 2009 23:52:50 +0000</pubDate>
		<guid isPermaLink="false">http://paul.donnelly.org/?p=96#comment-19</guid>
		<description>awesome post! keep up the gr8 work with yql and pipes! I&#039;m experimenting with yql execute and pipes to help create neighborhood sms alerts. thanks again. look forward to more posts.</description>
		<content:encoded><![CDATA[<p>awesome post! keep up the gr8 work with yql and pipes! I&#8217;m experimenting with yql execute and pipes to help create neighborhood sms alerts. thanks again. look forward to more posts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

