You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Mike Tutkowski <mi...@solidfire.com> on 2013/05/18 03:30:22 UTC
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: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
Re: TO suffix
Posted by Mike Tutkowski <mi...@solidfire.com>.
I see...that makes sense...it looks like the example I threw out there was
a subset of when TO is used.
Thanks!
On Fri, May 17, 2013 at 7:41 PM, Pranav Saxena <pr...@citrix.com>wrote:
> 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:mike.tutkowski@solidfire.com]
> *Sent:* Saturday, May 18, 2013 7:08 AM
> *To:* Pranav Saxena
> *Cc:* dev@cloudstack.apache.org
> *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 <pr...@citrix.com>
> wrote:****
>
> TO is probably Transfer Object .****
>
>
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: Saturday, May 18, 2013 7:00 AM
> To: dev@cloudstack.apache.org
> 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: mike.tutkowski@solidfire.com
> o: 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: mike.tutkowski@solidfire.com****
>
> o: 303.746.7302****
>
> Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>
> *™*****
>
--
*Mike Tutkowski*
*Senior CloudStack Developer, SolidFire Inc.*
e: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
RE: TO suffix
Posted by Pranav Saxena <pr...@citrix.com>.
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:mike.tutkowski@solidfire.com]
Sent: Saturday, May 18, 2013 7:08 AM
To: Pranav Saxena
Cc: dev@cloudstack.apache.org
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 <pr...@citrix.com>> wrote:
TO is probably Transfer Object .
-----Original Message-----
From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com<ma...@solidfire.com>]
Sent: Saturday, May 18, 2013 7:00 AM
To: dev@cloudstack.apache.org<ma...@cloudstack.apache.org>
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: mike.tutkowski@solidfire.com<ma...@solidfire.com>
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: mike.tutkowski@solidfire.com<ma...@solidfire.com>
o: 303.746.7302
Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play>(tm)
Re: TO suffix
Posted by Mike Tutkowski <mi...@solidfire.com>.
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 <pr...@citrix.com>wrote:
> TO is probably Transfer Object .
>
> -----Original Message-----
> From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
> Sent: Saturday, May 18, 2013 7:00 AM
> To: dev@cloudstack.apache.org
> 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: mike.tutkowski@solidfire.com
> o: 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: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*™*
RE: TO suffix
Posted by Pranav Saxena <pr...@citrix.com>.
TO is probably Transfer Object .
-----Original Message-----
From: Mike Tutkowski [mailto:mike.tutkowski@solidfire.com]
Sent: Saturday, May 18, 2013 7:00 AM
To: dev@cloudstack.apache.org
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: mike.tutkowski@solidfire.com
o: 303.746.7302
Advancing the way the world uses the
cloud<http://solidfire.com/solution/overview/?video=play>
*(tm)*