Re: Data validation, mapping, and error handling

ASP.NET validation server controls perform both Client and Server side
validation (automatically). I would consider that a pretty good feature to
emulate in another solution (my original point)

Maurice O'Prey


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Raul A. Jager W.
Sent: 30 June 2008 14:25
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Data validation, mapping, and error handling

The reason for redundant validation is that client validation
(Javascript) is a lot faster for the user because it can do it field by
field, without calling the server.
But, it is very easy to skip over the validation in the windows client.
That's why you also need the validation in the server.
____________________________________________________________________________
_______
Nathan Andelin wrote:

Maurice O'Prey wrote:
You could add auto JavaScript generation to handle stage 1...
It seems like the next logical step to me ;-)

Are you suggesting Javascript generation from DDS or SQL DDL
specifications? If so, that would be redundant validation, and I'm not
sure what purpose that would serve.

Except that it reminds me of something I learned in college. If you
have a procedure that fails 1% of the time, and you back it up with a
redundant procedure that fails 1% of the time, the resulting failure
rate is 1% times 1% = .01%. So if .Net interfaces have a 1% failure
rate, then I can see Microsoft's rationale for redundant validation ;-)

Nathan.