Peter:
The OMG frequently run into the problem of running out of terms. During the
business object work a couple of years ago, a suggestion was made to
describe your notion of a service - the word is:
Appliance
It is useful to think about "appliance" in terms of an electrical or hi-fi
appliance. An appliance has to wired together with other appliances to
properly function, it carries with it the notion of expressing conformance
with a contract (i.e. interface), and the notion of replaceability.
Cheers, Steve.
Peter Donald [mailto:[EMAIL PROTECTED]]
> In light of the new Services API I think long term we will have to further
> clarify our terminology. The notion of "service" I introduced
> basically was equivelent to a java interface + a version number.
>
> So long term it would be best to refine this term - unfortunately I
> couldn't think of any other equivelent words that didn't have just as much
> baggage. Some possible ones I cam up with were
>
> * Plug
> * Contract
> * Protocol
> * VersionedInterface
> * Connector
> * Communicator
> etc...
>
> None of them really floats my boat - except perhaps plug. Other than that
> not sure. Thoughts?
>
> Cheers,
>
> Pete
>
> *-----------------------------------------------------*
> | "Faced with the choice between changing one's mind, |
> | and proving that there is no need to do so - almost |
> | everyone gets busy on the proof." |
> | - John Kenneth Galbraith |
> *-----------------------------------------------------*
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
