When we start using components it is common to start grouping related functions into separate components which effectively become reusable libraries of functions. Typically these objects do not maintain state (they only contain functions) and are often placed into the application scope so the functions are available everywhere.
As we progress further along in OO design our objects start to become more focused in their responsibilities, start to maintain state and look a lot less like libraries of code. At this point we need a nice way to get our objects to “talk to each other” as the library doesn’t quite fit any longer.
A technique for achieving this is called Dependency Injection, which is a complicated name for a fairly simple idea. ColdSpring is a Dependency Injection framework which helps you get objects taking to each other in a well designed way.
A good place to start: what is dependency injection?
Then check out the beginners guide to ColdSpring by Brian Rinaldi.
ColdSpring · Dependency Injection
Robert Rawlins · August 31, 2009 at 11:31 am
ColdSpring really is an awesome tool, IoC is just such a powerful mechanism once you get used to using it, I’m glad to see you plugging it.
Two more features of ColdSpring that don’t really get enough attention are the RemoteProxys that allow you to create versions of your components that are accessible as web service, really very helpful, we use that a great deal here.
The other killer feature is AOP, I’m sure many people reading this are only just getting to grips with OOP but once you’ve got your head around it please take a look at the AOP stuff in ColdSpring, it’ll blow your mind! Really so very powerful.
Rob
Kevan Stannard · August 31, 2009 at 11:50 am
Thanks Rob. Those will be a couple of good topics to cover on the site.
Brian Rinaldi · September 1, 2009 at 4:33 pm
Thanks for the link. @Robert – both those topics are covered in my tutorial.