Ok, working on a project here where we are discussing what is a best approach to retrieving data to Flex. In our case we have a model domain with say 20 objetcs. All of them can be composed into one 'fat' composite object. From a Flex UI perspective, is it better to:
A) fetch the whole fat composed object and return it to the user allowing the user to operate on all facets of the model domain without returning to the DB. Once the user mashes SAVE somewhere, the whole fat composed object is sent to the server for processing. or B) fetch pieces of the object seperately as the user requests them. Thus the FlexUI is working with smaller pieces, but many more trips to the DB. What are your thoughts and experiences? Obviously the quick answer is 'it depends', we wouldn't want to use A if the composite object is really bulky, I'm thinking about the less extreme cases. For example, a composite object such as a Customer object that has say a array of Address objects, a array of Orders with each Order having a array of Products, and basic customer info. -- Douglas Knudsen http://www.cubicleman.com this is my signature, like it?
