On 4/5/07, J MacKay <[EMAIL PROTECTED]> wrote:
>LightWire is simpler – if you want to know HOW a DI engine works, >the core code in LightWire is under 400 lines so it is a great way >to look under the hood and really get the pattern That's a plus. Personally, I like knowing _how_ things work, not just that they _do_ work. Makes it easier to understand the capabilities (and limitations) of a given tool and of course change or fix things as needed. (Not that anything ever changes in an application ;)
:-) I understand where you're coming from with this statement ... I really do. Still i think there's value in not painting yourself into a do-it-yourselfer corner where you'd only use a framework you have the capability to understand and build / modify yourself. I'm speaking from experience here! The more i am exposed to OO, the more i see that there is a lot of value in using solutions that others have developed. It seems to be how the OO world works to a great extent. By all means, do your best to understand what's going on under the hood of a framework. It's a great way to learn. But you can use a framework without understanding all it's inner workings in the same way you use your computer without understanding the electronics, or your car without understanding how to repair it when it breaks down. There's a lot of value in just being able to sit down in the drivers seat and simply use the damn thing to get where you need to go.
I don't know about anyone else, but it leaves my mind free to concentrate on >getting the job done, instead of thinking about architecture issues all the >time and wondering if i'm doing it the right way or setting myself up to get >stuck in some corner down the line. Well put. That was my biggest concern about committing to a framework. Knowing so little about them, I didn't want to paint myself into a corner by choosing the wrong framework or something that was not well suited to the task at hand.
There are lots of very experienced and very smart people using the main ColdFusion frameworks, so i don't think you can go wrong here. I myself am not that smart a programmer, really, i'm just being honest here. But I'm currently using a combination of ModelGlue, (mainly because at the time the documentation available made it easier to pick up, but also because i found it a little simpler to understand than Mach II), ColdSpring, and Transfer. It's a great combination. But you can also combine Mach II or Fusebox, ColdSpring or Litewire, and Reactor. The only major corner you may need to be careful of is if you're thinking of providing a Flex user interface down the line and starting with an HTML user interface and you build your app using ModelGlue, MachII or Fusebox. You only want to make sure in this case to build out a service layer - seek advice how to do that properly when the time comes from someone who's done it. That way, both Flex and your framework controller can access the same service layer, and you don't wind up having to duplicate work. A minor corner in Transfer that is easily correctable also comes to mind. By default, all Transfer Objects are cached in memory. When getting into Transfer, recognize that default behavior from the outset, and scale back the ObjectCache configuration appropriately while building in any query caching you need yourself. It's a minor thing, but if you misunderstand and think you're caching queries rather than object instances in transfer, you may need to rework things a bit if you find yourself crashing your server as the app scales out. I don't know if that's helpful, but those are the only 2 common corners that i can think of that one can paint oneself into by using one of the frameworks.
It wasn't until i just tried it, following a few examples, that it became > suddenly really simple to understand, and very useful. Thanks for all of the comments. Time to dive in. I'm going to run some simple examples with ColdSpring, Transfer and Lightwire and see if a lightbulb goes off. I'm sure I'll be back later with more questions :) -- ------------------------------ Don't be flakey. Get Yahoo! Mail for Mobile<http://us.rd.yahoo.com/evt=43909/*http://mobile.yahoo.com/mail>and always stay connected<http://us.rd.yahoo.com/evt=43909/*http://mobile.yahoo.com/mail>to friends. You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
