We have the same here... Consumer with addresses, contact methods, payments methods and billing schedules... we fetch the entire object graph, let the user make any changes he wants and then send back in one shot on commit() using FDS. Dimitrios Gianninas RIA Developer Optimal Payments Inc.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Douglas Knudsen Sent: Thursday, December 21, 2006 9:51 AM To: [email protected] Subject: [flexcoders] big composite object or smaller pieces of the pie? 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 <http://www.cubicleman.com> this is my signature, like it? -- WARNING ------- This electronic message and its attachments may contain confidential, proprietary or legally privileged information, which is solely for the use of the intended recipient. No privilege or other rights are waived by any unintended transmission or unauthorized retransmission of this message. If you are not the intended recipient of this message, or if you have received it in error, you should immediately stop reading this message and delete it and all attachments from your system. The reading, distribution, copying or other use of this message or its attachments by unintended recipients is unauthorized and may be unlawful. If you have received this e-mail in error, please notify the sender. AVIS IMPORTANT -------------- Ce message électronique et ses pièces jointes peuvent contenir des renseignements confidentiels, exclusifs ou légalement privilégiés destinés au seul usage du destinataire visé. L'expéditeur original ne renonce à aucun privilège ou à aucun autre droit si le présent message a été transmis involontairement ou s'il est retransmis sans son autorisation. Si vous n'êtes pas le destinataire visé du présent message ou si vous l'avez reçu par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses pièces jointes, de votre système. La lecture, la distribution, la copie ou tout autre usage du présent message ou de ses pièces jointes par des personnes autres que le destinataire visé ne sont pas autorisés et pourraient être illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en aviser l'expéditeur.
