Comments on: The Component Burden http://elegantcode.com/2008/12/14/the-component-burden/ Sun, 14 Mar 2010 12:04:09 -0500 http://wordpress.org/?v=2.8.6 hourly 1 By: Davy Brion http://elegantcode.com/2008/12/14/the-component-burden/comment-page-1/#comment-39740 Davy Brion Mon, 15 Dec 2008 20:00:11 +0000 http://elegantcode.com/?p=1692#comment-39740 i go for transient as much as possible as well, but that doesn't relieve you from the burden of having to dispose them properly (if they are disposable) of course, if you're using a Castle build with the component burden fix already included, then this is not an issue anymore i go for transient as much as possible as well, but that doesn’t relieve you from the burden of having to dispose them properly (if they are disposable)

of course, if you’re using a Castle build with the component burden fix already included, then this is not an issue anymore

]]> By: Bill Pierce http://elegantcode.com/2008/12/14/the-component-burden/comment-page-1/#comment-39731 Bill Pierce Mon, 15 Dec 2008 17:33:05 +0000 http://elegantcode.com/?p=1692#comment-39731 I don't think you should ever dispose of an instance you didn't create. Why would you? You have no way of knowing whom else is using it regardless of the prescense of an IoC container. I agree, if you are using a container, it should be properly disposing of instances as needed. You pointed out this feature was a long time coming to Windsor because it is a complex issue when you mix dependencies of differing lifestyles. Because of this I try to go the opposite direction than most users and strive for all transient components unless object creation is very expensive. -Bill I don’t think you should ever dispose of an instance you didn’t create. Why would you? You have no way of knowing whom else is using it regardless of the prescense of an IoC container.

I agree, if you are using a container, it should be properly disposing of instances as needed. You pointed out this feature was a long time coming to Windsor because it is a complex issue when you mix dependencies of differing lifestyles. Because of this I try to go the opposite direction than most users and strive for all transient components unless object creation is very expensive.

-Bill

]]> By: Sergio Pereira http://elegantcode.com/2008/12/14/the-component-burden/comment-page-1/#comment-39727 Sergio Pereira Mon, 15 Dec 2008 16:12:14 +0000 http://elegantcode.com/?p=1692#comment-39727 Funny. I thought I had read it carefully... Oh, well, consider my comment just an echo, then, or a reinforcement of the issue. Funny. I thought I had read it carefully… Oh, well, consider my comment just an echo, then, or a reinforcement of the issue.

]]> By: Davy Brion http://elegantcode.com/2008/12/14/the-component-burden/comment-page-1/#comment-39720 Davy Brion Mon, 15 Dec 2008 13:35:46 +0000 http://elegantcode.com/?p=1692#comment-39720 I did actually mention that problem :) "Suppose someone makes the change to the dependency and then configures the IoC container to always return a singleton instance of this dependency. If nobody thinks about the fact that the Controller still assumes a Transient lifecycle of the dependency, the disposal of the dependency will not be removed from the Controller class. Once a Controller instance is created, and then disposed, it will try to dispose the instance of its dependency, which will cause problems because that instance is supposed to be used by other objects as well!" I did actually mention that problem :)

“Suppose someone makes the change to the dependency and then configures the IoC container to always return a singleton instance of this dependency. If nobody thinks about the fact that the Controller still assumes a Transient lifecycle of the dependency, the disposal of the dependency will not be removed from the Controller class. Once a Controller instance is created, and then disposed, it will try to dispose the instance of its dependency, which will cause problems because that instance is supposed to be used by other objects as well!”

]]> By: Sergio Pereira http://elegantcode.com/2008/12/14/the-component-burden/comment-page-1/#comment-39719 Sergio Pereira Mon, 15 Dec 2008 13:33:21 +0000 http://elegantcode.com/?p=1692#comment-39719 Davy, another problem with releasing the dependency yourself is that you are assuming the dependency is indeed transient. If in the future you change that dependency's implementation and configuration because you need or prefer that it is, say, a singleton then you'll have to go back into your controllers and stop disposing that type of dependency. I did not know component burden had been added to the trunk. I guess that means we are getting closer to castle 1.0 RTM, FWIW. Davy, another problem with releasing the dependency yourself is that you are assuming the dependency is indeed transient. If in the future you change that dependency’s implementation and configuration because you need or prefer that it is, say, a singleton then you’ll have to go back into your controllers and stop disposing that type of dependency. I did not know component burden had been added to the trunk. I guess that means we are getting closer to castle 1.0 RTM, FWIW.

]]> By: Davy Brion http://elegantcode.com/2008/12/14/the-component-burden/comment-page-1/#comment-39665 Davy Brion Sun, 14 Dec 2008 15:37:31 +0000 http://elegantcode.com/?p=1692#comment-39665 interesting, thx for the tip :) interesting, thx for the tip :)

]]> By: Jonathan http://elegantcode.com/2008/12/14/the-component-burden/comment-page-1/#comment-39664 Jonathan Sun, 14 Dec 2008 15:21:18 +0000 http://elegantcode.com/?p=1692#comment-39664 You may want to look at another popular IoC container, Autofac. It handles the disposal problem perfectly. You may want to look at another popular IoC container, Autofac. It handles the disposal problem perfectly.

]]>