God, looks like I've been asleep since the nineties or something. The AspectWerkz mailing lists were, all of a sudden, flooded by messages related to Pico and Nano containers.
Like, over a night's sleep I suddenly can't understand a word that's
being said on such messages. Feels awful, but that's OK, that's what
makes us move our lazy asses out there and learn new things. And what I
found out was pretty interesting:
"PicoContainer is very simple container for very simple
components. It honors the Inversion of control pattern (IoC) in a
way that we calling it type 3 IoC.
PicoContainer components declare their needs in their
constructor.
A PicoContainer resolves needs at time on instantiation of the
component. We have a restriction in that PicoContainer components
must
only have one constructor. We don't think that is a bad restriction.
Especially as the XP "change it when you need to" has not delivered a
use case that would preclude this design yet. We also can't allow
primitives in the constructor." (from the website)
I'll blog more about those fellas as I understand them better, but,
so far, the big question is: is an IoC framework useful? If yes, could
you please elaborate? :)
Previous Topic
