My 2 cents
I agree with Dave Watts, CF is a glue. Any methodology you use for any
server-side language your going to have to use not only the application
server tier, but the client and database tiers. If the database is designed
right and is set up with constraints and triggers, can cut done on your
coding.
I use fusebox, I try not to get to complicated with it. We use it for its
directory structure and filename convention. This gives us what I think it
brings to CF the best, is a method that can help you reuse code and track
down bugs and coding problems fast. What I'm trying to say is I like to keep
it simple on the code and let any other devices do the big hog work like the
database. If the database can do it with triggers or store procs then hand
it off to your DB guy. Do not validate code on the server-side do as much as
you can on the client side first.
I do believe that Fusebox is here to stay. I think it will just have to
change in some areas to flow with any big changes in CF.
Shawn Regan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
