taco said > Centralized data validation is certainly a good idea, but I would store the > meta data for the fields in a XML file instead of defining it by a prefix.
the validation obj will be accessible by all forms across many sites. So do you mean that each form from each site should also pass an xml string detailing which field needs what validation? If not, what do you mean exactly? if i can do without the prefix it will make my life easier >I don't think all your objects should go into one CFC, the error.cfc should >handle all errors and not just those for your form, so that should be a CFC >on its own IMHO It will, but ive only just started out! I am hoping to have a global error object, form object, validation object, and ive also thought about doing a global DAO. any others i could implement? your views greg said >My understanding is that there is still some way to go >before you could even start considering cfml an OO language oh yes, i agree, but i thought that there may have been more emphasis on teaching the benefits of oop and what can be done in cf so far (thus i could have concentrated on these methods from the start). joined the various lists you suggested, tuned brain to sponge mode and off i go! cheers for the info guys jamo --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
