Josh Sled <[email protected]> writes: > This month we'll have a small set of mini-presentations. > > Josh Sled will talk about dependency injection and inversion of control. > > Brian Hunter will talk about Flash/Flex development using Linux > command-line tools.
Thanks to the handful of people who showed up; the small size lent itself to what I thought were a couple of great interactive discussions. Special thanks to Jonathan Ferguson and FIREHOSE for hosting. One other thing I had intended to point out is that if you squint, you could even imagine shared library resolution as a form of dependency injection: an application or library declares "I am dependent on an implementation of 'libc.so.6'", and the DI framework^W^Wlinker (through LD_PRELOAD, the normal dependency resolution process, &c.) provides the implementation ((g)libc-2.11.3.so or dietlibc or ulibc or …). And those modules are likewise already "injected" with their dependent modules. Okay, you have to squint a fair bit. ;) But the core of the approach is more broadly applicable than just in the Java and .Net environments … any system that wants to configure a graph of interdependent modules can leverage it. -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo ${a}@${b}
