[flexcoders] Flex application architecture for data validation

[gault17]

We are trying to come up with a strategy for data validation in our 
Flex application. Our current approach is to perform basic data 
validation (valid values for each field) on the client side and invoke 
server-side objects to perform more thorough validation such as 
relational edits(e.g. if field x  100, field y must have value AA). 
However, I'm wondering whether an approach that favors more client-side 
validation would be better. Something like validate on the client side 
as long as no call to the server is required to retrieve additional 
data or access external services. The answer, I imagine, is it 
depends. But I'd be interested to know what factors to consider and 
what guidelines others are using for their Flex data capture 
applications. Thanks

Gary Ault
Bureau of Labor Statistics 





--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
Yahoo! Groups Links

* To visit your group on the web, go to:
http://groups.yahoo.com/group/flexcoders/

* To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]

* Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
 

Re: [flexcoders] Flex application architecture for data validation

[Abdul Qabiz]

I think, validations which has sensitive information, should not be done on client side. For example, any business logic that reveals some sensitive algorithm, don't do it on clientYou can do normal data validations, like numbers, date, email, credit card number validations(to validate if user has entered correct pattern for a VISA card but don't connect to gateway API from client directly, rather do it through a server-side script on your server), etc.
I mean things which you see are done on client, can be done..But not sensitive things...-abdulOn 3/6/06, gault17 
[EMAIL PROTECTED] wrote:We are trying to come up with a strategy for data validation in our
Flex application. Our current approach is to perform basic datavalidation (valid values for each field) on the client side and invokeserver-side objects to perform more thorough validation such asrelational edits(
e.g. if field x  100, field y must have value AA).However, I'm wondering whether an approach that favors more client-sidevalidation would be better. Something like validate on the client side
as long as no call to the server is required to retrieve additionaldata or access external services. The answer, I imagine, is itdepends. But I'd be interested to know what factors to consider and
what guidelines others are using for their Flex data captureapplications. ThanksGary AultBureau of Labor Statistics--Flexcoders Mailing ListFAQ: 
http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txtSearch Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups Links
* To visit your group on the web, go to:http://groups.yahoo.com/group/flexcoders/* To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]* Your use of Yahoo! Groups is subject to:http://docs.yahoo.com/info/terms/







--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com








  
  
SPONSORED LINKS
  
  
  

Web site design development
  
  
Computer software development
  
  
Software design and development
  
  


Macromedia flex
  
  
Software development best practice
  

   
  







  
  
  YAHOO! GROUPS LINKS



  Visit your group "flexcoders" on the web.
  To unsubscribe from this group, send an email to:[EMAIL PROTECTED]
  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.