Thanks, everybody :) As I delve into the code more, I'm trying to pick up little details like this, as well.
On Tue, Mar 12, 2013 at 11:18 AM, Kelven Yang <kelven.y...@citrix.com>wrote: > MO names after VMware management object > > Kelven > > On 3/12/13 2:50 AM, "Prasanna Santhanam" <t...@apache.org> wrote: > > >DAO - Data Access Object > >TO - Transfer Object > > > >Do we have MOs? > > > >On Tue, Mar 12, 2013 at 02:40:18AM +0530, Kelven Yang wrote: > >> Per my understanding, VO stands for Value Object, however, it is really > >> used as Entity Object (CRM term) in CloudStack > >> > >> Kelven > >> > >> On 3/11/13 2:00 PM, "Mike Tutkowski" <mike.tutkow...@solidfire.com> > >>wrote: > >> > >> >Hi, > >> > > >> >Probably a really easy question for someone out there: > >> > > >> >StoragePoolVO...What does the VO stand for? > >> > > >> >Thanks! > >> > > >> >-- > >> >*Mike Tutkowski* > >> >*Senior CloudStack Developer, SolidFire Inc.* > >> >e: mike.tutkow...@solidfire.com > >> >o: 303.746.7302 > >> >Advancing the way the world uses the > >> >cloud<http://solidfire.com/solution/overview/?video=play> > >> >*?* > > > >-- > >Prasanna., > > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *™*