<?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 on: Fun with Fluent Interfaces</title>
	<atom:link href="http://caseywatson.com/2009/10/14/fun-with-fluent-interfaces/feed/" rel="self" type="application/rss+xml" />
	<link>http://caseywatson.com/2009/10/14/fun-with-fluent-interfaces/</link>
	<description>keepin' it real... real simple.</description>
	<lastBuildDate>Wed, 17 Feb 2010 01:27:26 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://caseywatson.com/2009/10/14/fun-with-fluent-interfaces/comment-page-1/#comment-119</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 14 Oct 2009 20:38:29 +0000</pubDate>
		<guid isPermaLink="false">http://caseywatson.com/?p=255#comment-119</guid>
		<description>Thanks for the feedback, bro.  

This particular block of code is being used within a service where I spin up several &quot;agents&quot; upon startup.  I suppose I could have done it the way you suggest, but this seemed a bit cleaner at the time.

Your comment did make me notice one thing, however.  I was just spinning up a plain vanilla thread and kicking it off.  That could get pretty heavy especially if I&#039;m spinning up several hundred threads on startup.  I modified it to take advantage of the thread pool which is optimized for this sort of thing.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback, bro.  </p>
<p>This particular block of code is being used within a service where I spin up several &#8220;agents&#8221; upon startup.  I suppose I could have done it the way you suggest, but this seemed a bit cleaner at the time.</p>
<p>Your comment did make me notice one thing, however.  I was just spinning up a plain vanilla thread and kicking it off.  That could get pretty heavy especially if I&#8217;m spinning up several hundred threads on startup.  I modified it to take advantage of the thread pool which is optimized for this sort of thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wil Bloodworth</title>
		<link>http://caseywatson.com/2009/10/14/fun-with-fluent-interfaces/comment-page-1/#comment-118</link>
		<dc:creator>Wil Bloodworth</dc:creator>
		<pubDate>Wed, 14 Oct 2009 20:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://caseywatson.com/?p=255#comment-118</guid>
		<description>Casey,

Nice read.  Love the &quot;fluent&quot; stuff.

Instead of using a full-blown thread and then putting it to sleep, you could just use a Timer instance and set the initial delay so that the timer will fire off at the desired time.  It&#039;s just another way of skinning the same feline.

- Wil</description>
		<content:encoded><![CDATA[<p>Casey,</p>
<p>Nice read.  Love the &#8220;fluent&#8221; stuff.</p>
<p>Instead of using a full-blown thread and then putting it to sleep, you could just use a Timer instance and set the initial delay so that the timer will fire off at the desired time.  It&#8217;s just another way of skinning the same feline.</p>
<p>- Wil</p>
]]></content:encoded>
	</item>
</channel>
</rss>
