<?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: Protecting Your Application From Remote Problems</title> <atom:link href="http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/feed/" rel="self" type="application/rss+xml" /><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/</link> <description>inquisitive: adjective. given to inquiry, research, or asking questions; eager for knowledge; intellectually curious</description> <lastBuildDate>Wed, 08 Feb 2012 11:42:42 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <item><title>By: Davy Brion</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-101600</link> <dc:creator>Davy Brion</dc:creator> <pubDate>Fri, 07 Oct 2011 09:14:00 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-101600</guid> <description>no, the whole point of using a circuit breaker is to avoid having your request-handling threads block because it&#039;s waiting for failing remote services... the idea is that it should fail early once the remove service is known to be down.  Retrying automatically would defeat the purpose, unless you have a non-blocking delay between the retries.</description> <content:encoded><![CDATA[<p>no, the whole point of using a circuit breaker is to avoid having your request-handling threads block because it&#8217;s waiting for failing remote services&#8230; the idea is that it should fail early once the remove service is known to be down.  Retrying automatically would defeat the purpose, unless you have a non-blocking delay between the retries.</p> ]]></content:encoded> </item> <item><title>By: Lengtche</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-101598</link> <dc:creator>Lengtche</dc:creator> <pubDate>Thu, 06 Oct 2011 21:04:00 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-101598</guid> <description>Awesome article.How do I use the service breaker? So I inject my service (which gets intercepted) and call some method (say Connect()). If I simply call my method and it fails I&#039;ll get an exception, fair enough. Do I need to run my method in a loop or something until it&#039;s successful?</description> <content:encoded><![CDATA[<p>Awesome article.</p><p>How do I use the service breaker? So I inject my service (which gets intercepted) and call some method (say Connect()). If I simply call my method and it fails I&#8217;ll get an exception, fair enough. Do I need to run my method in a loop or something until it&#8217;s successful?</p> ]]></content:encoded> </item> <item><title>By: Nikos Baxevanis</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-99125</link> <dc:creator>Nikos Baxevanis</dc:creator> <pubDate>Tue, 26 Apr 2011 22:21:00 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-99125</guid> <description>nice, so it&#039;s just the design that changes</description> <content:encoded><![CDATA[<p>nice, so it&#8217;s just the design that changes</p> ]]></content:encoded> </item> <item><title>By: Davy Brion</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-99123</link> <dc:creator>Davy Brion</dc:creator> <pubDate>Tue, 26 Apr 2011 08:10:00 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-99123</guid> <description>so each state implementation doesn&#039;t have to call the base ActUponException like it did in the previous version i linked to</description> <content:encoded><![CDATA[<p>so each state implementation doesn&#8217;t have to call the base ActUponException like it did in the previous version i linked to</p> ]]></content:encoded> </item> <item><title>By: Nikos Baxevanis</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-99086</link> <dc:creator>Nikos Baxevanis</dc:creator> <pubDate>Mon, 25 Apr 2011 16:48:00 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-99086</guid> <description>Great!
Question: Why you increase the failure count outside of the ActUponException in this version of the CircuitBreaker? ;-)</description> <content:encoded><![CDATA[<p>Great!<br
/> Question: Why you increase the failure count outside of the ActUponException in this version of the CircuitBreaker? <img
src='http://d18sni7re4ly7f.cloudfront.net/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /></p> ]]></content:encoded> </item> <item><title>By: Mitja</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-56667</link> <dc:creator>Mitja</dc:creator> <pubDate>Mon, 30 Aug 2010 20:39:00 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-56667</guid> <description>container.Register...what is container here? How can i get it?</description> <content:encoded><![CDATA[<p>container.Register&#8230;</p><p>what is container here? How can i get it?</p> ]]></content:encoded> </item> <item><title>By: Steve Degosserie</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-22182</link> <dc:creator>Steve Degosserie</dc:creator> <pubDate>Tue, 07 Jul 2009 11:07:54 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-22182</guid> <description>Nice Davy. Some previous implementations:
http://blog.yoot.be/index.php/2008/06/12/circuitbreaker-interceptor/
http://timross.wordpress.com/2008/02/10/implementing-the-circuit-breaker-pattern-in-c/
http://timross.wordpress.com/2008/02/17/implementing-the-circuit-breaker-pattern-in-c-part-2/</description> <content:encoded><![CDATA[<p>Nice Davy. Some previous implementations:<br
/> <a
href="http://blog.yoot.be/index.php/2008/06/12/circuitbreaker-interceptor/" rel="nofollow">http://blog.yoot.be/index.php/2008/06/12/circuitbreaker-interceptor/</a><br
/> <a
href="http://timross.wordpress.com/2008/02/10/implementing-the-circuit-breaker-pattern-in-c/" rel="nofollow">http://timross.wordpress.com/2008/02/10/implementing-the-circuit-breaker-pattern-in-c/</a><br
/> <a
href="http://timross.wordpress.com/2008/02/17/implementing-the-circuit-breaker-pattern-in-c-part-2/" rel="nofollow">http://timross.wordpress.com/2008/02/17/implementing-the-circuit-breaker-pattern-in-c-part-2/</a></p> ]]></content:encoded> </item> <item><title>By: Arjan&#8217;s World &#187; LINKBLOG for July 6, 2009</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-22133</link> <dc:creator>Arjan&#8217;s World &#187; LINKBLOG for July 6, 2009</dc:creator> <pubDate>Mon, 06 Jul 2009 13:02:53 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-22133</guid> <description>[...] Protecting Your Application From Remote Problems - Davy Brion &#8216; If you have a web application which communicates with a remote service, it’s important to protect that web application from any problems the remote service might be dealing with &#8216; [...]</description> <content:encoded><![CDATA[<p>[...] Protecting Your Application From Remote Problems &#8211; Davy Brion &#8216; If you have a web application which communicates with a remote service, it’s important to protect that web application from any problems the remote service might be dealing with &#8216; [...]</p> ]]></content:encoded> </item> <item><title>By: Jack</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-22116</link> <dc:creator>Jack</dc:creator> <pubDate>Mon, 06 Jul 2009 09:51:52 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-22116</guid> <description>Oh, so powerful!
Why Microsoft don&#039;t give us some functions like this?</description> <content:encoded><![CDATA[<p>Oh, so powerful!<br
/> Why Microsoft don&#8217;t give us some functions like this?</p> ]]></content:encoded> </item> <item><title>By: Reflective Perspective - Chris Alcock &#187; The Morning Brew #383</title><link>http://davybrion.com/blog/2009/07/protecting-your-application-from-remote-problems/comment-page-1/#comment-22100</link> <dc:creator>Reflective Perspective - Chris Alcock &#187; The Morning Brew #383</dc:creator> <pubDate>Mon, 06 Jul 2009 07:30:39 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1443#comment-22100</guid> <description>[...] Protecting Your Application From Remote Problems - Davy Brion talks about the importance of insulating your applications from problems in the remote systems they call, and looks at the concept of the Circuit Breaker. [...]</description> <content:encoded><![CDATA[<p>[...] Protecting Your Application From Remote Problems &#8211; Davy Brion talks about the importance of insulating your applications from problems in the remote systems they call, and looks at the concept of the Circuit Breaker. [...]</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 5/17 queries in 0.008 seconds using disk: basic
Object Caching 472/479 objects using disk: basic
Content Delivery Network via Amazon Web Services: CloudFront: d18sni7re4ly7f.cloudfront.net

Served from: davybrion.com @ 2012-02-09 03:14:23 -->
