Sean is correct, you may not be ready for step like this. if you don't see what CS/IoC can do for you and your code applications now you should step back and look at what it does and why (if you do know, explain here and see it ties up). I think part of the problem could be that you are new to it and you are thinking like a "traditional" ColdFusion developer rather than an OO or a software engineer.
As Sean noted, read up on Fatories, but also to get a better understanding of OO, and IoC before you even think about applying to you (ColdFusion) code / problems (again, if you think you "have it" post here and use the list for what it was designed to be - a good sounding board :-) -----Original Message----- From: Sean Corfield To: [email protected] Sent: Sat Sep 22 07:27:16 2007 Subject: [coldspring-dev] The advantages of Coldspring On 9/21/07, Snake <[EMAIL PROTECTED]> wrote: > I was hoping for some enlightenment to show me i'm missing something. ColdSpring is one of those things that you can't really understand until you've hit the problems it solves - and then its benefits are obvious... Which makes it really hard to explain. The best I can do right now is point you at my "Managing ColdFusion Components with Factories" presentation and see if any of that resonates with you. If not, you're not ready for ColdSpring. http://corfield.org/articles/cfobj_factories.pdf -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
