It's a class that transfers data from one tier to another (e.g., from the business logic tier to the resource layer) is a Transfer Object and is suffixed with TO e.g., LoadBalancerTO.
From: Mike Tutkowski [mailto:[email protected]] Sent: Saturday, May 18, 2013 7:08 AM To: Pranav Saxena Cc: [email protected] Subject: Re: TO suffix Ah, OK...Would you be able to say design wise how these differ from VOs? VOs are used to read from and write to the DB. Maybe TOs are for transferring data to agent code or something? On Fri, May 17, 2013 at 7:32 PM, Pranav Saxena <[email protected]<mailto:[email protected]>> wrote: TO is probably Transfer Object . -----Original Message----- From: Mike Tutkowski [mailto:[email protected]<mailto:[email protected]>] Sent: Saturday, May 18, 2013 7:00 AM To: [email protected]<mailto:[email protected]> Subject: TO suffix Hi, I believe VO = Value Object. Can someone tell me what TO stands for? :) Thanks! -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: [email protected]<mailto:[email protected]> o: 303.746.7302<tel:303.746.7302> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *(tm)* -- Mike Tutkowski Senior CloudStack Developer, SolidFire Inc. e: [email protected]<mailto:[email protected]> o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>(tm)
