| Because that's a dependency that I'd rather avoid. The VerityController is an independent object I wrote months ago and it has no external dependencies at all. I know that ColdSpring makes managing dependencies easier, but where I can allow the argument value to BE the dependency and not require an internal dependency between objects I think, at least under some circumstances, I can build a more robust system out of non-coupled objects. In a simple system like this it's no big deal, really... but in a large system with many separate libraries, it seems to me that being able to allow the framework to handle dependency down to the argument level could be a huge boon. That's my rationale, anyway. How much merit it has remains to be seen... Laterz, J ------------------------------------------------ Jared C. Rypka-Hauer Continuum Media Group LLC Member, Team Macromedia - ColdFusion "That which does not kill me makes me stranger." - Yonah Schmeidler On Apr 21, 2006, at 1:03 PM, Sean Corfield wrote:
|
- [coldspring-dev] bindings in CS XML - a question Jared Rypka-Hauer
- [coldspring-dev] bindings in CS XML - a question Dave Ross
- [coldspring-dev] bindings in CS XML - a question Sean Corfield
- [coldspring-dev] bindings in CS XML - a question Dave Ross
- [coldspring-dev] bindings in CS XML - a question Matt Williams
- [coldspring-dev] bindings in CS XML - a question Jared Rypka-Hauer
- [coldspring-dev] bindings in CS XML - a question Sean Corfield
- [coldspring-dev] bindings in CS XML - a question Mark Mandel
