On Wed, Jun 2, 2010 at 6:51 PM, Steve Onnis <st...@cfcentral.com.au> wrote: > I want to be able to have a single file as the entry point, a proper > index.cfm file that actually does something and then from there be able to > handle my own calls to a controller that does what I need it to do.
Well, that's the very definition of no-framework then. There are no frameworks you will like. They all take control of the basic flow - that's kind of the point of frameworks. All of the frameworks out there - from Fusebox to ColdBox and everything in between - take the 'action' (or fuseaction or event) in the URL and take control away from your index.cfm and route it through either conventions or configuration to code that the framework invokes and then the framework selects which files to display to build the view (sometimes with hints from the developer thru API calls). Frameworks aren't for everyone. Developers that want to keep total control over the flow of their application and tend to every detail of how their code works just don't like frameworks. Other developers value the standardization that frameworks bring and understand that a lot of the plumbing and boilerplate code is a waste of their expensive time and they prefer to focus on the interesting parts of building an application using an approach that other developers can easily pick up - particularly where that approach is a publicly documented one and you can find other developers who already know the approach. -- Sean A Corfield -- (904) 302-SEAN Railo Technologies, Inc. -- http://getrailo.com/ An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood -- You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaus...@googlegroups.com. To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en.
