>>>>> "CD" == Chris Devers <[EMAIL PROTECTED]> writes:
CD> On Thu, 26 May 2005, Uri Guttman wrote: >> [...] the common falacy of using javascript for data validation which >> leads to dropping that from the server. CD> What fallacy is this ? CD> There's nothing wrong with using Javascript to validate form data, and CD> if you do it well, you can provide better and more immediate feedback to CD> the user without having to make round trips back & forth with the server CD> to do the same thing. The application ends up feeling more responsive CD> and the bandwidth load on the server is reduced. I see nothing at all CD> wrong with using Javascript this way. CD> The fallacy is failing to validate things on the *server*. that was my point. i may have not stated it well. but the OP's mentioning of using javashit to force some default value or something on an unchecked radio button is related to this. since you can submit via LWP and not run any JS, the server must always validate. so the JS answer is just plain no good. CD> Properly done, validation should happen on *both* sides, but minimally CD> it has to happen on your side. it doesn't ever have to be done on the client side. that is totally a 'user unfriendly' design choice and irrelevant to the OP's problem. it can be nicer for complex forms when it tells you that you missed a required value and such. many times it can be annoying but that is about UI and not validation. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
