Transfer Objects are not Value Objects, really!!
Tags: Coldfusion, Flex
Very short post, after a colleague I work with has called them a VO again I have decided to make this a little more public.
</more>
Sun changed their minds on this pattern, and I do not know how continued or even got it wrong in the world of ColdFusion and PHP. But 75% of the time anyone who asks a question on a VO is very much reminded that sun adopted them as Transfer Objects because it was too confusing to what a value object actually is.
So if you are a flex and/or ColdFusion developer I really wish you would begin to call your VO's as TO's unless you really mean the true definition of a Value Object. But to date every time I hear the term VO, I know they mean TO.
Enough said, I know who started it in the ColdFusion world. And I wish that person would step forward and say they got it wrong.
-
Let's go one step further and force people to call them DTO's instead of just TO's.
Like most other things wrong in Flex, I think we can blame the proliferation of "Value Object" as a term on Cairngorm...# Posted By Joe Rinehart | 11/25/09 4:59 AM
TweetBacks