Kay Smoljak wrote:
On 5/2/05, Chad Renando <[EMAIL PROTECTED]> wrote:
2. What do you guys do for form validation: client-side, server-side or both? Is there automation inherent to these flash forms I keep hearing about?
Both, absolutely, and if there's not enough time to do both, server-side only. There is some automation available in all kinds of CFForms, and it's actually pretty cool.
Just to add to that, I think the ideal solution is to do both client side and server side validation, AND make both methods express identical UI behaviour. On the client side, you keep the validation code (JS) separate from the error-handling code (JS/DHTML/CSS). So whether errors are caught client side or server side, you invoke the same error-handling code to feedback to the user. Personally, I only do simple validation client side to weed out the common errors and do the real stringent validation server side. Too hard to do in JS, which is rather cumbersome in string-handling.
-- Regards: Ayudh
+----------------------------------------------------------------+ | SOAP is the glue! Hook up your server directly to your bank. | | Connect to VeriPay xServ, the Australian Payments Web Service. | | Reliable, Secure, FAST: http://www.xilo.com/xserv | +----------------------------------------------------------------+
--- 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/
