<?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 Codex.org</title>
	<atom:link href="http://www.codex.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codex.org</link>
	<description>Coding, ramblings, and more</description>
	<lastBuildDate>Mon, 26 Mar 2012 12:09:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Comment on RightScale API 1.0 with Ruby &#8212; Authentication by jobu</title>
		<link>http://www.codex.org/2012/03/07/rightscale-api-1-0-with-ruby-authentication/comment-page-1/#comment-9299</link>
		<dc:creator>jobu</dc:creator>
		<pubDate>Mon, 26 Mar 2012 12:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.codex.org/?p=209#comment-9299</guid>
		<description>I looked at the &quot;rest_connection&quot; gem, and did not find that it provided that much functionality to me. Overall, it was overly complicated for what it was attempting to do. Ruby provides easy mechanisms to do all that is provided by the rest_connection gem. 

Currently, API 2.0 is only available to you if you work for RightScale. So, unless we switch from the Amazon cloud, I am stuck with API 1.0. To this end, I am just writing a wrapper to properly handle logging in, and then handling the cookie, so that I am not authenticating every time. Dropping a subsection to handle put, get, delete requests was simple enough after doing that.

Any update on when API 2.0 will be available?

I look forward to a better authentication method. Currently, having to have an account just for API access is a little on the funny side.</description>
		<content:encoded><![CDATA[<p>I looked at the &#8220;rest_connection&#8221; gem, and did not find that it provided that much functionality to me. Overall, it was overly complicated for what it was attempting to do. Ruby provides easy mechanisms to do all that is provided by the rest_connection gem. </p>
<p>Currently, API 2.0 is only available to you if you work for RightScale. So, unless we switch from the Amazon cloud, I am stuck with API 1.0. To this end, I am just writing a wrapper to properly handle logging in, and then handling the cookie, so that I am not authenticating every time. Dropping a subsection to handle put, get, delete requests was simple enough after doing that.</p>
<p>Any update on when API 2.0 will be available?</p>
<p>I look forward to a better authentication method. Currently, having to have an account just for API access is a little on the funny side.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on RightScale API 1.0 with Ruby &#8212; Authentication by Ryan J. Geyer</title>
		<link>http://www.codex.org/2012/03/07/rightscale-api-1-0-with-ruby-authentication/comment-page-1/#comment-9285</link>
		<dc:creator>Ryan J. Geyer</dc:creator>
		<pubDate>Sun, 18 Mar 2012 18:23:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.codex.org/?p=209#comment-9285</guid>
		<description>Thanks for the article on consuming the RightScale API.

If you&#039;re using the RightScale API in Ruby, there are a couple different gems which make the process (including authentication) a bit easier.  For API v1.0 use &#039;rest_connection&#039; (https://rubygems.org/gems/rest_connection) and for API v1.5/2.0 use right_api_client (https://rubygems.org/gems/right_api_client).

You&#039;ll also be happy to know that some changes to the authentication for the RightScale API is coming.  Rather than requiring basic authentication and a cookie exchange, a token based authentication is in the works so look for that soon.</description>
		<content:encoded><![CDATA[<p>Thanks for the article on consuming the RightScale API.</p>
<p>If you&#8217;re using the RightScale API in Ruby, there are a couple different gems which make the process (including authentication) a bit easier.  For API v1.0 use &#8216;rest_connection&#8217; (<a href="https://rubygems.org/gems/rest_connection" rel="nofollow">https://rubygems.org/gems/rest_connection</a>) and for API v1.5/2.0 use right_api_client (<a href="https://rubygems.org/gems/right_api_client" rel="nofollow">https://rubygems.org/gems/right_api_client</a>).</p>
<p>You&#8217;ll also be happy to know that some changes to the authentication for the RightScale API is coming.  Rather than requiring basic authentication and a cookie exchange, a token based authentication is in the works so look for that soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Atlas Shrugged &#8211; Part I by Michael R. Brown</title>
		<link>http://www.codex.org/2011/05/24/atlas-shrugged-part-i/comment-page-1/#comment-2617</link>
		<dc:creator>Michael R. Brown</dc:creator>
		<pubDate>Sat, 04 Jun 2011 08:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.codex.org/?p=152#comment-2617</guid>
		<description>The book&#039;s prophetic quality is as strange as it is frightening.</description>
		<content:encoded><![CDATA[<p>The book&#8217;s prophetic quality is as strange as it is frightening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting Solaris network information by jobu</title>
		<link>http://www.codex.org/2010/04/08/solaris-network-troubleshooting/comment-page-1/#comment-232</link>
		<dc:creator>jobu</dc:creator>
		<pubDate>Sat, 10 Apr 2010 02:21:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.codex.org/?p=72#comment-232</guid>
		<description>You must have been working with a limited number of sparc based servers. The ones I have are all over the place. Wait till you get my read about Solaris x86 grub support. That will just make your head spin.</description>
		<content:encoded><![CDATA[<p>You must have been working with a limited number of sparc based servers. The ones I have are all over the place. Wait till you get my read about Solaris x86 grub support. That will just make your head spin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting Solaris network information by Brian Baggett</title>
		<link>http://www.codex.org/2010/04/08/solaris-network-troubleshooting/comment-page-1/#comment-228</link>
		<dc:creator>Brian Baggett</dc:creator>
		<pubDate>Thu, 08 Apr 2010 21:31:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.codex.org/?p=72#comment-228</guid>
		<description>I forgot that nugget about Solaris. I always used to hate that network interfaces weren&#039;t aliased. On Linux, you had eth0. On Solaris x86, you had bcm0, etc. It was terrible. On SPARC&#039;s it wasn&#039;t bad (on the ones I had access to) because it was always hme0.</description>
		<content:encoded><![CDATA[<p>I forgot that nugget about Solaris. I always used to hate that network interfaces weren&#8217;t aliased. On Linux, you had eth0. On Solaris x86, you had bcm0, etc. It was terrible. On SPARC&#8217;s it wasn&#8217;t bad (on the ones I had access to) because it was always hme0.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Under old management but new changes by Bouti</title>
		<link>http://www.codex.org/2010/01/30/under-old-management-but-new-changes/comment-page-1/#comment-2</link>
		<dc:creator>Bouti</dc:creator>
		<pubDate>Mon, 01 Feb 2010 14:41:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.codex.org/?p=3#comment-2</guid>
		<description>Like this design ;)</description>
		<content:encoded><![CDATA[<p>Like this design <img src='http://www.codex.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

