On Feb 3, 2004, at 7:57 AM, Sean Scott wrote: > I handle conditional logic and use the Mach-II framework in a slightly > different manner. ... > Otherwise much of the controller function is included in an Manager > Object which acts as a "gatekeeper and traffic controller".
I don't think this is necessarily a very good way to handle things. You have much more flexibility if you have a lot of small components that you 'plug together' in the XML file. ** Well I think it's a matter of choice based on the needs of your application. The application in question is structure in such a way that the core CFCs won't change. Additional functionality will be added by way of modules. These modules use the MachII xml file to simply communicate back to the user and allow the user communicate back to it via form submissions. Is this structure the right one for every application, perhaps not. Then again MachII isn't either. ** > An added bonus is that for future enhancements, you can leave the > machii.xml file alone (using it only for input output functions). The XML file is the *easy* part to change - you don't want to be changing *code* for future enhancements unless you need to. ** Yes but as you know any changes to any file increase the chance of an unintended result or bug. So by therefore restricting access and standardizing the way enhancement are introduced to the application you can manage that risk. In addition if you have multiple developer working on various modules, there won't be any checking in or out of the xml file. They can all work on there separate components, using the xml for communication back to the user. This particular method was devised to solve a particular issue and thus is applicable in a specific context. However developers can only benefit fro seeing a number of different structures from which they are free to chose which apply to their particular situation. Sean Scott ** ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED] ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
