I must admit I have never heard of validation on the database before, and I am not sure how one would actually do that. But yes your concerns about validation when using extJS is a valid argument to not do that.
The reason being is that server validation is a must because there was a time when people had browsers that did not support JS, and more recently would turn it off. So if any of those conditions are met then server validation would be a must, but if they are running extJS then the likely hood that JS is not present will be extremely slim. Regards, Andrew Scott http://www.andyscott.id.au/ > -----Original Message----- > From: Richard White [mailto:[email protected]] > Sent: Thursday, 23 September 2010 6:27 PM > To: cf-talk > Subject: 3 layers of validation? > > > Hi, > > when at university i read that it is always best to have 3 layers of validation > (client,server,database) which i have been doing in my applications. > > I have now built a few web applications using extjs, which i think has > excellent validation features. > > I am developing a new web application and starting to wonder why all the > additional work is needed to put all the same validation into the server and > the database when extjs does so well. > > i understand there must be a lot of security on the server and database, and > any variables accepted by the server can have the type attribute set, but is it > really necessary to replicate validation on all 3 layers? > > i have never had the validation on the server or database fire purely because > extjs is so good! > > would appreciate others thoughts on this > > thanks ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:337353 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
