Peter, I have not yet read the remainder of this thread, but if you are new to this list, I would suggest you go back a few months and search for form validation messages. There were quite a few of them related to how/where/when form data is validated. I started a few because I had/have the same questions as you.
I finally just tried a method (using string-typed variables) and was somewhat pleased with the result. I still don't have a good taste for that solution because the argument types are all strings rather than their actual datatypes, but having typed arguments was also the problem. Now, I will read the rest of this thread. M!ke -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter H Sent: Saturday, May 07, 2005 11:13 AM To: [email protected] Subject: [CFCDev] Form Validation Hi guys, This may be a little of topic but possibly not. With regards to form validation, client side validation is helpful but can be side-stepped as can the use of hidden fields, so logically this makes server side validation a neccessity. Consequently my code ends up riddled with validation logic; is it the right type, does it fit in a range, does it match a pattern etc. Is there a design pattern I could use that would make doing this sort of thing cleaner or possibly a server-side validation library / cfc available to help with this? Cheers, Pete (aka lad4bear) ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
