<?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: Integrating Your IOC Container With Agatha</title> <atom:link href="http://davybrion.com/blog/2009/11/integrating-your-ioc-container-with-agatha/feed/" rel="self" type="application/rss+xml" /><link>http://davybrion.com/blog/2009/11/integrating-your-ioc-container-with-agatha/</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/11/integrating-your-ioc-container-with-agatha/comment-page-1/#comment-101147</link> <dc:creator>Davy Brion</dc:creator> <pubDate>Mon, 05 Sep 2011 08:28:00 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1966#comment-101147</guid> <description>not sure what you mean with it not supporting lifetime... lifecycles are actually explicitly dealt with in the interfaceas for disposal: only 2 of the supported containers support automatic disposal of disposable transient dependencies.  All the others don&#039;t, regardless of whether you use something like Agatha or its container abstraction.  The disposal burden rests entirely upon you in those cases.  Agatha&#039;s container abstraction at least uses the ability with the containers that implement it.&quot;The container should be responsible for what is is good at: registration, resolving dependencies, cleanup and disposal.&quot;the whole point of this abstraction is to use the actual container for all of that (with the possible exception of disposal, since most containers don&#039;t handle that properly) but to not force you, the consumer, to worry about correct registration of all required components.i&#039;m pretty sure the time-savings of not having to deal with support-requests from people who misconfigured one of the components are worth it, not to mention the fact that configuration of Agatha is now a very minimal and easy step for users.Also, Agatha&#039;s IContainer implementation is meant to be used _by Agatha_, not by the user.  A user can use it, but i&#039;d expect, and recommend, users to use their containers directly without any abstractions.  All they need to do is pass their container instance to Agatha&#039;s configuration object and that&#039;s all there is to it.</description> <content:encoded><![CDATA[<p>not sure what you mean with it not supporting lifetime&#8230; lifecycles are actually explicitly dealt with in the interface</p><p>as for disposal: only 2 of the supported containers support automatic disposal of disposable transient dependencies.  All the others don&#8217;t, regardless of whether you use something like Agatha or its container abstraction.  The disposal burden rests entirely upon you in those cases.  Agatha&#8217;s container abstraction at least uses the ability with the containers that implement it.</p><p>&#8220;The container should be responsible for what is is good at: registration, resolving dependencies, cleanup and disposal.&#8221;</p><p>the whole point of this abstraction is to use the actual container for all of that (with the possible exception of disposal, since most containers don&#8217;t handle that properly) but to not force you, the consumer, to worry about correct registration of all required components.</p><p>i&#8217;m pretty sure the time-savings of not having to deal with support-requests from people who misconfigured one of the components are worth it, not to mention the fact that configuration of Agatha is now a very minimal and easy step for users.</p><p>Also, Agatha&#8217;s IContainer implementation is meant to be used _by Agatha_, not by the user.  A user can use it, but i&#8217;d expect, and recommend, users to use their containers directly without any abstractions.  All they need to do is pass their container instance to Agatha&#8217;s configuration object and that&#8217;s all there is to it.</p> ]]></content:encoded> </item> <item><title>By: JarrettV</title><link>http://davybrion.com/blog/2009/11/integrating-your-ioc-container-with-agatha/comment-page-1/#comment-101116</link> <dc:creator>JarrettV</dc:creator> <pubDate>Fri, 02 Sep 2011 15:32:00 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1966#comment-101116</guid> <description>I&#039;m not a fan your design.  I prefer the approach the ASP.NET MVC team took.For example, it has too many methods to implement.  Also, your approach does not support lifetime or unit of work easily.  Your approach only supports disposal with two containers.  All the other container implementations leak memory.I also feel like scanning assemblies should be the responsibility of the container and not Agatha.  Why not make explicit interface for outsourcing these implementations to the container.  NServiceBus does the same thing and it is simply unintuitive for the developer.The container should be responsible for what is is good at: registration, resolving dependencies, cleanup and disposal.</description> <content:encoded><![CDATA[<p>I&#8217;m not a fan your design.  I prefer the approach the ASP.NET MVC team took.</p><p>For example, it has too many methods to implement.  Also, your approach does not support lifetime or unit of work easily.  Your approach only supports disposal with two containers.  All the other container implementations leak memory.</p><p>I also feel like scanning assemblies should be the responsibility of the container and not Agatha.  Why not make explicit interface for outsourcing these implementations to the container.  NServiceBus does the same thing and it is simply unintuitive for the developer.</p><p>The container should be responsible for what is is good at: registration, resolving dependencies, cleanup and disposal.</p> ]]></content:encoded> </item> <item><title>By: Avoiding Memory Leaks With NServiceBus And Your Own Castle Windsor Instance &#124; The Inquisitive Coder &#8211; Davy Brion&#39;s Blog</title><link>http://davybrion.com/blog/2009/11/integrating-your-ioc-container-with-agatha/comment-page-1/#comment-29343</link> <dc:creator>Avoiding Memory Leaks With NServiceBus And Your Own Castle Windsor Instance &#124; The Inquisitive Coder &#8211; Davy Brion&#39;s Blog</dc:creator> <pubDate>Sun, 21 Feb 2010 19:38:42 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1966#comment-29343</guid> <description>[...] as its IoC container, but it’s been changed to support multiple containers in a similar manner as Agatha does it.&#160; Agatha however, was originally developed with Castle Windsor as its IoC container, and as [...]</description> <content:encoded><![CDATA[<p>[...] as its IoC container, but it’s been changed to support multiple containers in a similar manner as Agatha does it.&#160; Agatha however, was originally developed with Castle Windsor as its IoC container, and as [...]</p> ]]></content:encoded> </item> <item><title>By: Reducing Code Coupling – Inversion of Control &#124; GrantPalin.com</title><link>http://davybrion.com/blog/2009/11/integrating-your-ioc-container-with-agatha/comment-page-1/#comment-25024</link> <dc:creator>Reducing Code Coupling – Inversion of Control &#124; GrantPalin.com</dc:creator> <pubDate>Fri, 15 Jan 2010 07:04:40 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1966#comment-25024</guid> <description>[...] be a need to have a common interface that offers such additional functionality; Davy Brion&#8217;s Agatha project does [...]</description> <content:encoded><![CDATA[<p>[...] be a need to have a common interface that offers such additional functionality; Davy Brion&#8217;s Agatha project does [...]</p> ]]></content:encoded> </item> <item><title>By: Davy Brion</title><link>http://davybrion.com/blog/2009/11/integrating-your-ioc-container-with-agatha/comment-page-1/#comment-23053</link> <dc:creator>Davy Brion</dc:creator> <pubDate>Sun, 29 Nov 2009 21:54:19 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1966#comment-23053</guid> <description>@Andreasglad to know other people are using this approach as well... while i was working on this i couldn&#039;t help think &quot;i can&#039;t be the only one who wants to do it like _this_&quot;</description> <content:encoded><![CDATA[<p>@Andreas</p><p>glad to know other people are using this approach as well&#8230; while i was working on this i couldn&#8217;t help think &#8220;i can&#8217;t be the only one who wants to do it like _this_&#8221;</p> ]]></content:encoded> </item> <item><title>By: Andreas</title><link>http://davybrion.com/blog/2009/11/integrating-your-ioc-container-with-agatha/comment-page-1/#comment-23052</link> <dc:creator>Andreas</dc:creator> <pubDate>Sun, 29 Nov 2009 21:48:45 +0000</pubDate> <guid
isPermaLink="false">http://davybrion.com/blog/?p=1966#comment-23052</guid> <description>This is exactly how we do it in NServiceBus, perhaps is time for a &quot;Common Service Configuration&quot; project :)Anyways, interesting posts. Good luck with Agatha!</description> <content:encoded><![CDATA[<p>This is exactly how we do it in NServiceBus, perhaps is time for a &#8220;Common Service Configuration&#8221; project <img
src='http://d18sni7re4ly7f.cloudfront.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p><p>Anyways, interesting posts. Good luck with Agatha!</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 3/11 queries in 0.005 seconds using disk: basic
Object Caching 403/406 objects using disk: basic
Content Delivery Network via Amazon Web Services: CloudFront: d18sni7re4ly7f.cloudfront.net

Served from: davybrion.com @ 2012-02-08 19:21:07 -->
