Aaron, Would you mind explaining some of the acronyms you threw around? Specifically: what is DI/ioC? What is ORM (I should know my CFUG just did a preso on Transfer I think, but I missed out)? You say, they all solve different problems. What are those problems, and how do these frameworks go about solving them? I can see that LW is LightWire, but you didn't tell us uninitiated what CS stood for. I personally understood the string of controller frameword initials you threw down, but for someone asking what to use two-letter initials probably don't help much.
Can you expand please? :o) Thanks, Chris Aaron Roberson wrote: > First, you need to understand that there are different kinds of > frameworks. There are controller frameworks (such as MG, M2, FB, CB, > etc), DI/ioC frameworks (CS and LW) and ORM frameworks (Reactor, > Transfer and oB). > > I like ColdBox for my controller framework (most documented, and > suites my programming style the best), LightWire (LW) for my DI/ioC > framework (gives you the flexibility of switching over to CS later > down the road if you like using an XML config), and since I am on > BlueDragon I am not using any ORM frameworks, but I can't wait for Nic > Tunney to update objectBreeze to v2 - once he does I will be adopting > it. > > In general, controller frameworks provide a solution to the same > problem, DI/ioC frameworks provide a solution to another problem, and > ORM frameworks provide a solution to yet another problem. How they are > configured and some of their features may very. > > HTH, > Aaron > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:278483 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4