doing some thinking here, yeah amazing for a Monday eh? I have an application with a multi-part form. My first thought was to use CFCs to model the form, having a parent CFC with child CFCs for each 'section'. Now, to do this all data in a CFC has to be exposed/manipulated. IE getters/setters for every property in the CFC, or use of setProperty/getProperty methods. After thinknig on this I'm convincing myself that this is poor use of CFCs, that is, there does not seem to be a compelling reason to use OO stuffs for this. I can see creating a CFC or two for the biz logics, but not the form itself, have say a formhandler.cfc.
Thoughts from the masters on this? Is having a CFC with a one-to-one mapping of form fields to properties in the CFC worthwhile or just overhead? I'm guessing this is a loaded opinionated question, but still, I'd like to see some thoughts. Cheers! -- Douglas Knudsen Alltel ACI Rapid Response Team "To fear love is to fear life, and those who fear life are already three parts dead." Bertrand Russell ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word '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]
