<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pattern on Marko Apfel</title><link>http://blog.marko-apfel.de/tags/pattern/</link><description>Recent content in Pattern on Marko Apfel</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 03 May 2011 05:46:00 +0200</lastBuildDate><atom:link href="http://blog.marko-apfel.de/tags/pattern/index.xml" rel="self" type="application/rss+xml"/><item><title>Castle Windsor: order of configurations and resulting resolvings</title><link>http://blog.marko-apfel.de/posts/castle-windsor-order-of-configurations-and-resulting-resolvings/</link><pubDate>Tue, 03 May 2011 05:46:00 +0200</pubDate><guid>http://blog.marko-apfel.de/posts/castle-windsor-order-of-configurations-and-resulting-resolvings/</guid><description>&lt;p&gt;If different implementations for the same interface are specified without named keys, then a resolving is made in order of the configurations. So the first fitting implementation is taken.&lt;/p&gt;
&lt;p&gt;Different implementations for the same interface is a typical scenario for patterns like “chain of responsibility” and “decorator”. If you want to describe such a chain you could use the next handler as a constructor- parameter in the actual one.&lt;/p&gt;</description></item></channel></rss>