[Arp] Difference between Value Objects and Models?
matt at gradiation.co.uk
Thu Mar 16 04:57:06 PST 2006
Aral, Sorry to cross post but could you please offer your view about VO's in the current post titled 'The right way to use VO/TO's '
I'm interested to know if VO's should only be used for transfering data, how should data be held in model? Wouldn't the model contain collections of VO's?
From: "Keith Salisbury" <keithsalisbury at gmail.com>
Sent: 16 March 2006 07:48
To: "General List for Ariaware RIA Platform users and developers" <Arp at ariaware.com>
Subject: Re: [Arp] Difference between Value Objects and Models?
I think the term "Transfer Object" is much better. Its far more
explicit about what the purpose of the object is.
We should all try to promote adoption of this term i believe as it
will make it easier for new comers to understand more quickly...
On 3/2/06, Aral Balkan wrote:
> Hi Regina,
> Perhaps the term "Value Object" is not as clear as "Transfer Object".
> Basically, the model should be where you keep the data and VOs/TOs are
> what you use when you want to transfer/move data to carry out a unit of
> business logic. The idea behind a VO is that it contains all the data
> necessary to carry out a specific unit of business logic.
> Both of them getting registered via the same class is actually
> confusing. I need to refactor that so that the name is more generic.
> Arp mailing list
> Arp at ariaware.com
keithsalisbury at gmail.com
Arp mailing list
Arp at ariaware.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Arp