Kevin Mukhar wrote:
>
> Another solution is to let the user click submit twice
> and detect the problem on the server side.
> ...
> Admittedly, this is harder to implement than a few
> lines of javascript in the html.
>
Kevin, would you agree that you've got to check on
the server-side in any case?
Web browsers running over the Internet aren't exactly
reliable clients, so you have to assume bad things
happen on the way to the server. And then there's the
people who run with javascript turned off...
Client-side validation is a nice optimization that
makes the user experience smoother, and maybe saves
some wear and tear on the server. But it's optional.
Server-side validation isn't optional for an enterprise
system.
It's a tradeoff: up-front engineering time vs the cost
of doing a quick and dirty job. Sometimes it's just not
worth the effort, but support calls are very expensive,
and one bad experience can lose you a customer.
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
