<?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 JonHoman.com</title>
	<atom:link href="http://blog.jonhoman.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jonhoman.com</link>
	<description>Walking the Long Road</description>
	<lastBuildDate>Fri, 15 Apr 2011 17:24:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Simple Way to Autoscale Heroku Workers by Dave Hoover</title>
		<link>http://blog.jonhoman.com/simple-way-to-autoscale-heroku-workers/#comment-687</link>
		<dc:creator>Dave Hoover</dc:creator>
		<pubDate>Fri, 15 Apr 2011 17:24:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonhoman.com/?p=391#comment-687</guid>
		<description>JC Grubbs just told me about HireFire&lt;/a&gt;, which seems like it might be helpful.</description>
		<content:encoded><![CDATA[<p>JC Grubbs just told me about HireFire, which seems like it might be helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Simple Way to Autoscale Heroku Workers by Carl Thuringer</title>
		<link>http://blog.jonhoman.com/simple-way-to-autoscale-heroku-workers/#comment-681</link>
		<dc:creator>Carl Thuringer</dc:creator>
		<pubDate>Fri, 08 Apr 2011 03:39:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonhoman.com/?p=391#comment-681</guid>
		<description>Pretty sweet! I&#039;ve been loving Heroku since I deployed my blog on it and this is exactly the kind of clever cost-saving magic that I expect from a flexible app hosting cloud. 
I don&#039;t currently need workers or extra dynos, but knowing this I&#039;ll be alert for occasions where apps I&#039;m working on could benefit from a periodic boost in services.</description>
		<content:encoded><![CDATA[<p>Pretty sweet! I&#8217;ve been loving Heroku since I deployed my blog on it and this is exactly the kind of clever cost-saving magic that I expect from a flexible app hosting cloud.<br />
I don&#8217;t currently need workers or extra dynos, but knowing this I&#8217;ll be alert for occasions where apps I&#8217;m working on could benefit from a periodic boost in services.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Getting Started with webmock and VCR by Myron Marston</title>
		<link>http://blog.jonhoman.com/getting-started-with-webmock-and-vcr/#comment-673</link>
		<dc:creator>Myron Marston</dc:creator>
		<pubDate>Mon, 21 Mar 2011 05:24:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonhoman.com/?p=361#comment-673</guid>
		<description>Nice post :).

I&#039;d recommend against configuring WebMock (i.e. via &quot;require &#039;webmock/rspec&#039;&quot;), unless you specifically need to interface with WebMock directly.  One of the benefits of VCR is that it works at a higher level of abstraction and allows you to switch stubbing libraries if you need to.  Also, WebMock pollutes the rspec namespace a bit (or the global namespace if you include it globally).  See &lt;a href=&quot;http://twitter.com/#!/ryanbigg/status/25751785707&quot; rel=&quot;nofollow&quot;&gt;this tweet&lt;/a&gt;.

Rather than setting a default record mode of :none, and using :new_episodes in your tests, you might consider using the new &lt;a href=&quot;http://relishapp.com/myronmarston/vcr/v/1-7-1/dir/record-modes/once&quot; rel=&quot;nofollow&quot;&gt;once&lt;/a&gt; record mode.  It&#039;s also the default now.

If you ever figure out what your issue with using VCR w/ cucumber tags, let me know--I can update the documentation to warn others of any gotchas or pitfalls.</description>
		<content:encoded><![CDATA[<p>Nice post <img src='http://blog.jonhoman.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> .</p>
<p>I&#8217;d recommend against configuring WebMock (i.e. via &#8220;require &#8216;webmock/rspec&#8217;&#8221;), unless you specifically need to interface with WebMock directly.  One of the benefits of VCR is that it works at a higher level of abstraction and allows you to switch stubbing libraries if you need to.  Also, WebMock pollutes the rspec namespace a bit (or the global namespace if you include it globally).  See <a href="http://twitter.com/#!/ryanbigg/status/25751785707" rel="nofollow">this tweet</a>.</p>
<p>Rather than setting a default record mode of :none, and using :new_episodes in your tests, you might consider using the new <a href="http://relishapp.com/myronmarston/vcr/v/1-7-1/dir/record-modes/once" rel="nofollow">once</a> record mode.  It&#8217;s also the default now.</p>
<p>If you ever figure out what your issue with using VCR w/ cucumber tags, let me know&#8211;I can update the documentation to warn others of any gotchas or pitfalls.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Faking HTTP requests with WebMock and VCR by Getting Started with webmock and VCR &#124; JonHoman.com</title>
		<link>http://blog.jonhoman.com/faking-http-requests-with-webmock-and-vcr/#comment-672</link>
		<dc:creator>Getting Started with webmock and VCR &#124; JonHoman.com</dc:creator>
		<pubDate>Sun, 20 Mar 2011 21:36:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonhoman.com/?p=349#comment-672</guid>
		<description>[...] JonHoman.com   Walking the Long Road    Skip to content HomeAboutContactProjects        &#8592; Faking HTTP requests with WebMock and VCR [...]</description>
		<content:encoded><![CDATA[<p>[...] JonHoman.com   Walking the Long Road    Skip to content HomeAboutContactProjects        &larr; Faking HTTP requests with WebMock and VCR [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Background Jobs in Rails with Resque by Jon</title>
		<link>http://blog.jonhoman.com/background-jobs-in-rails-with-resque/#comment-652</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Mon, 07 Feb 2011 15:43:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonhoman.com/?p=296#comment-652</guid>
		<description>Hey Chuck, thanks for pointing out that typo. I made the corresponding change in the code example.

I think I still like having the FeedParser code where it is. Being able to queue jobs is the first task I want to describe, and processing those jobs doesn&#039;t need to be in place to queue jobs. I think that&#039;s the point I wanted to convey.

Glad you got something out of the post.</description>
		<content:encoded><![CDATA[<p>Hey Chuck, thanks for pointing out that typo. I made the corresponding change in the code example.</p>
<p>I think I still like having the FeedParser code where it is. Being able to queue jobs is the first task I want to describe, and processing those jobs doesn&#8217;t need to be in place to queue jobs. I think that&#8217;s the point I wanted to convey.</p>
<p>Glad you got something out of the post.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

