I'm at a cross-roads with my Flex 2 /Cairngorm 2.0 application. Next week, I'll begin the actual Data Processing on my application.
I won't be using Flex Data Services for my application. I wanted to collect other people's thoughts on using the Data Model as a Value Object. My belief is that my application doesn't have enough complex data to warrant the additional overhead of a completely separate Value Object class. Are there limitations that I don't forsee if I go ahead and use the Model as a value Object? My plan was to: 1) Bind Controls to multiple Model instances in an Application Model. 2) Reference those instances to multiple models (RegistrationModel.as, MainFormModel.as, MyAccountModel.as, etc.). 3) Bind these smaller models as 'objects' 4) Pass those objects to the Command > Delegate > Server and vice versa. Thoughts and suggestions are appreciated. Best David Buhler
