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.
What fallacy is this ? There's nothing wrong with using Javascript to validate form data, and if you do it well, you can provide better and more immediate feedback to the user without having to make round trips back & forth with the server to do the same thing. The application ends up feeling more responsive and the bandwidth load on the server is reduced. I see nothing at all wrong with using Javascript this way. The fallacy is failing to validate things on the *server*. Whether or not validation happens on the client is immaterial to how robust a system is -- though, as noted above, using good client-side validation has UI and load benefits that are very worthwhile. On the other hand, not validating on the server is a problem because, as you say, whether or not you have validation running on the client, it can be circumvented, so you have to be sure about what you're working on on the part of the system that you do have complete control over. Properly done, validation should happen on *both* sides, but minimally it has to happen on your side. -- Chris Devers _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
