Hi,
In the containerkit stuff we currently use the term "ServiceDesignator" to
indicate a versioned interface. We also use the term "Service" to indicate
a service that one component is capable of providing to another component.
It is a superset of a ServiceDesignator as it includes an arbitrary set of
attributes.
The use of the term "service" may not be quite right because of the
associated semantic baggage of the term. Can anyone think of a better term?
If not is there any objections to using the term?
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"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: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
