Each of these terms (API, protocol, endpoint) often connotes different
expectations about the relationships and responsibilities of the
participants. For example, is there expected to be asymmetric
responsibilities (e.g. client-server) between them?, What about any
implied "contract" between them? What about cardinality (APIs are
generally one-to-one, whereas endpoints may be many-to-one, e.g publish
and subscribe). What about the potential for concurrency?
So there are many considerations and properties that each of these may
imply or for which there may be differentiating expectations based upon
the milieu in which each originated (OOP, network communications,
distributed objects, etc.).
In other words, the usage of these terms is not really interchangeable.
On 5/10/13 8:09 AM, glen e p ropella wrote:
On 05/10/2013 07:04 AM, Stephen Guerin wrote:
I'm seeing a rise in the use of "endpoints". Eg REST, SOAP and WMS endpoints
Do you mean in the sense of leaves of a graph?
============================================================
FRIAM Applied Complexity Group listserv
Meets Fridays 9a-11:30 at cafe at St. John's College
to unsubscribe http://redfish.com/mailman/listinfo/friam_redfish.com
