VOs hold values. Events are an appropriate way to signal value changes. DTOs transfer values between tiers.
99.9999% of the time, VOs and DTOs are the same. IE, the flex-side of a DTO is also used as a VO. Kit On Fri, Jan 22, 2010 at 2:45 PM, John Mason <[email protected]> wrote: > So having a discussion at lunch and figure I post this to the user group to > see what people think. > > I'm working on a AIR app that uses the Mate framework. The pattern has value > objects (VOs, also sometimes called data transfer objects). The VOs have > binding turn on at the class level. I didn't really think about it until > recently that I suspect those bindings weren't even needed in this > particular case, but I was also wondering if this was just a bad design > pattern to begin with. Should a VO even be allowed to fire off binding > events? > > Thoughts? > > John > [email protected] > > > > > ------------------------------------------------------------- > To unsubscribe from this list, simply email the list with unsubscribe in the > subject line > > For more info, see http://www.affug.com > Archive @ http://www.mail-archive.com/discussion%40affug.com/ > List hosted by http://www.fusionlink.com > ------------------------------------------------------------- > > > ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
