There are also those situations where you will have redundant validation for
critical fields. First on the client side so the user isn't sitting waiting for
the server side to come back with an error and second on the server to catch any
of those critical validations where the user modified the validation code on the
client for fraudulent reasons.
Kevin Mukhar <[EMAIL PROTECTED]> on 04/20/2001 10:38:21 AM
Please respond to "A mailing list for discussion about Sun Microsystem's Java
Servlet API Technology." <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Harvey A Smith/MSD/US/PBI)
Subject: Re: Question??
"Christopher K. St. John" wrote:
>
> Kevin, would you agree that you've got to check on
> the server-side in any case?
> ...
> Server-side validation isn't optional for an enterprise
> system.
Yes, exactly. Every design decision involves trade-offs. It's not a bad
solution to do client-side validation. But for a robust application
that's going to be open to the public, I lean towards doing most
validation on the server-side.
___________________________________________________________________________
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
___________________________________________________________________________
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
