Re: [Terminology]

["David M. Chizmadia" <davidch@ccpl.carr.lib.md.us>]

I hope everyone will forgive my denseness, but why don't we just call 
the thing invoking the ADO the "ADO Client??

-DMC

> Date:          Thu, 16 Jul 1998 17:09:14 -0400 (EDT)
> From:          Konstantin Beznosov <beznosov@baptisthealth.net>
> Reply-to:      Konstantin Beznosov <beznosov@baptisthealth.net>
> Subject:       Re: [Terminology]
> To:            hrac-rfp@cs.fiu.edu

> > Hi,
> > >
> > >What if we call the object, which calls ADO, an "application service" (AS)
> > >? 
> > Ok... as long as we agree that an "application service" might not be
> > "application" code... that is, it could be "infrastructure (such as a bof),
> > or it could in fact be the orb itself for some types of resources that have
> > meaning from a CORBA perspective(such as interfaces and/or operations)....
> 
> or an interceptor :)
> 
> I was going to give similar disclaimer but did not find right words.
> 
> > I make this point now because I think it will be important at some point to
> > realize that we don't really know architecturally who will be the "client
> > of the ado".  :-)
> 
> Good point.
> 
> > 
> > >In that case, we do not have to get confused who is a client and who is
> > >the target. A phrase "Application service invokes methods on ADO" will be
> > >correct no matter what role (client, target) the application service
> > >performs. 
> > Unless the "client" isn't an application service.... agree?
> 
> yes
> 
> Konstantin
> 
> ----------------
> Broadcast message to hrac-rfp from Konstantin Beznosov <beznosov@baptisthealth.net>.
> Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.
> 
> 
----------------
Broadcast message to hrac-rfp from "David M. Chizmadia" <davidch@ccpl.carr.lib.md.us>.
Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.