Some forms of validation are completely impractical with pure client side JS. One good example I've seen is when a user is registering for a new username on a system; many systems leave this to the server, but I've seen systems with very slick AJAX functionality that checks for an existing username as the user types, so they can avoid the round trip of "this username is in use pick another."
Regardless, when a team of developers has to maintain an app it's often easier to maintain one set of code that does a given task, rather than two. On 5/2/07, Dan G. Switzer, II wrote: > > It still confuses me on how you guys think adding pure client-side > validation is so difficult. From many of the comments on here, you'd think > it takes days to implement. -- mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2 Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:276723 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
