HiveMind (the only other DI container that I have any significant experience with) introduced me to the concept of service models. What a service model does is basically determine how and when a particular service is instantiated. For example, the “singleton” model (in HiveMind) ensures that a particular service is only instantiated...

This is the next article in a series about the process I am taking as I refactor the Net::SSH library to take advantage of dependency injection. In this installment, I’ll talk about what challenges I have faced as I’ve tried to refactor the “Key Exchange” algorithms, not only to make them “dependency...

This is the next article in a series about the process I am taking as I refactor the Net::SSH library to take advantage of dependency injection. In this installment, I’ll talk about what challenges I have faced as I’ve tried to refactor the “Key Exchange” algorithms, not only to make them “dependency...

Needle is now on RubyForge! That is to say, the source code is in CVS on RubyForge… still no packaged releases, but now that it is in CVS I feel better about hacking on it. I can now rollback to previous versions if my experiments go sour. :) (For those of you that don’t know: Needle is my new dependency injection container for...

Needle is now on RubyForge! That is to say, the source code is in CVS on RubyForge… still no packaged releases, but now that it is in CVS I feel better about hacking on it. I can now rollback to previous versions if my experiments go sour. :) (For those of you that don’t know: Needle is my new dependency injection container for...

This is the second in a series of articles that deal with refactoring the Net::SSH library to take advantage of dependency injection. The first was Net::SSH Refactoring Adventure. Because I am using Syringe, and because the Syringe API has not yet solidified, refactoring Net::SSH to use Syringe is something of an iterative process. For example,...

This is the second in a series of articles that deal with refactoring the Net::SSH library to take advantage of dependency injection. The first was Net::SSH Refactoring Adventure. Because I am using Syringe, and because the Syringe API has not yet solidified, refactoring Net::SSH to use Syringe is something of an iterative process. For example,...

The BYU Ruby Users Group was kind enough to allow me to give my Copland presentation this evening, as practice for the up-coming Ruby Conference. There were only four attendees, besides myself, which is about par for the course when it comes to attendance at BYU RUG meetings. Still, I was flattered to learn that one attendee, Jacob Fugal, is...

The BYU Ruby Users Group was kind enough to allow me to give my Copland presentation this evening, as practice for the up-coming Ruby Conference. There were only four attendees, besides myself, which is about par for the course when it comes to attendance at BYU RUG meetings. Still, I was flattered to learn that one attendee, Jacob Fugal, is...

Leon Breedt recently proposed a way to allow services to be refreshed automatically when their dependencies are altered, in Syringe (ruby-talk:116021, among others). Although I don’t think his proposed solution isn’t generally possible in Syringe, it did inspire me with another idea. My response to his post (ruby-talk:116040)...

Leon Breedt recently proposed a way to allow services to be refreshed automatically when their dependencies are altered, in Syringe (ruby-talk:116021, among others). Although I don’t think his proposed solution isn’t generally possible in Syringe, it did inspire me with another idea. My response to his post (ruby-talk:116040)...

This article is just the first in a series describing the steps I am going through to refactor Net::SSH to use dependency injection. I’m currently using the DI framework code-named Syringe to do the dirty work. (Note: that link for Syringe is temporary only, and may not be valid if you are reading this article more than a few weeks after...

I’ve recieved a few requests to log about my journeys through the Dependency Injection universe, especially as regards my usage of Copland. However, I’m currently investigating a new approach to DI, as proposed by Jim Weirich in a recent blog article. So, instead of following my usage of Copland, instead I’m going to log about...

I’ve recieved a few requests to log about my journeys through the Dependency Injection universe, especially as regards my usage of Copland. However, I’m currently investigating a new approach to DI, as proposed by Jim Weirich in a recent blog article. So, instead of following my usage of Copland, instead I’m going to log about...

Today, I witnessed something beautiful. Jim Weirich Jim has consented to let me use his design as the basis for the “next generation” of Copland. I’m thinking I may want to just create a whole new project, since Copland’s approach to DI is significantly different than Jim’s, and the two are not exactly compatible...