struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank W. Zammetti" <>
Subject Re: Which methodology is better?
Date Wed, 29 Dec 2004 17:16:19 GMT
This question is entirely dependent on what environment your developing for.

95% of my work these days is internal-only applications where we have, 
basically, a "captive" audience: IE and nothing else, configured from a 
central location and locked down.  For me, I can do thing that I would 
never consider doing otherwise, like 99% of validation on the 
client-side.  Look at it this way... If I KNOW I can safely do this, why 
not make the app that much faster and responsive and minimize the load 
on the server?

But, when I do develop for public consumption, it's a different mindset. 
  I still do as much client-side validation as possible for the same 
reasons as above, but now I have to do some server-side checking. 
Depending on what I'm validating I may have to do it all there too.

But it depends on your target audience, how well you know what's coming 
in.  It's not a straight-forward answer, either way.

Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies

Jim Barrows wrote:
>>-----Original Message-----
>>From: Manisha Sathe []
>>Sent: Wednesday, December 29, 2004 12:44 AM
>>Subject: Which methodology is better?
>>I am very used to HTML/JavaScript. Normally i do all 
>>validations on clientside through JavaScript.
>>i just started Struts framework and i understand that 
>>"DynaActionForm" is to have validation on cliend side. (till 
>>now using ActionForm only).
>>Normally what is the practice ? Which way is better ?
> Don't ever trust the client side.  I can cobble up a web page with no validation and
submit it to your site faster then you can say PeterPiperPickedAPeckOfPickledPeppers 5 times
> In general, leave nothing on the web page unless you absolutely have to.  Avoid Javascript
the way a politician avoids a lie detector.  It will save you a lot of heartache in the long
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
> .

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message