Thanks for the comments, Dan. One of the reasons I've been tinkering with the use of Ajax in the validation is to get a little experience working with it and with JS using jQuery.
I haven't made use of Ajax before and see this use (validation) as a relatively simple way to get my feet wet. And, actually, if I'm understanding what's happening correctly, the taconite plug-in displaying the results (either error messages, or in the case of a mortgage calculator, the calculation results) is updating only part of the page... it's not reloading the entire page. (I've got to test this technique on a full web page... I've only used it on a very simple form.) Not refreshing the page to display error messages or calculation results is the reason for using Ajax. The mortgage calculation form is halfway down a real estate property details page and if the page refreshed, the user would have to scroll down to the link again, and click it to have the form revealed just to check the results. I'll ultimately strive for the most efficient code, but for now I'm just trying to figure out how to work with Ajax and jQuery at all. So 50 percent of this is practical and 50 percent is educational. What I'm mostly concerned about now is that it seems that I have to implement two separate validation schemes to insure validation is always available, whether JS is turned or not, and that the forms are not hacked, which using CF will prevent. Rick -----Original Message----- From: Dan G. Switzer, II [mailto:[EMAIL PROTECTED] Sent: Sunday, April 15, 2007 5:09 PM To: CF-Talk Subject: RE: Client-side validation or Server-side Validation? Rick, >Does the JS and CF validation have to be totally independent >in functionality? It would seem so, if I'm concerned about a user >not being able to use forms. > >I've got a technique I'm working on that involves JS posting a form >back to the page it's on, then cfincluding a page of CF to validate >the form data. > >After validation, I'm using the taconite plug-in to place error messages. This method is terrible inefficient for general validation (required fields, validating values, etc.) Not only have you added several layers of complexity, but you're almost completely voiding the benefits of client-side validation. I also know from some of your example code posts on mailing lists, you were doing most of these AJAX validation during a blur event of a field. This is going to generate a lot of server traffic--traffic that isn't necessary. You should only be doing AJAX validation when you can not do the validation on the client-side (such as validating against a database.) Just make sure you using AJAX to solve real problems, not just so you can say you're using it. This means don't use AJAX to submit a form when you're just going to reload a page if it's successful. You're making your code unnecessarily complicated. It should be used when you're just going to update a portion of your DOM--loading in a document fragment. For example, if you have a commenting system similar to most blogs. Instead of reloading the entire page when a user enters a comment, you could post there comment (and any new comments since their page loaded) and insert that document fragment. -Dan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:275295 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
