Proximity
From APIDesign
(Difference between revisions)
JaroslavTulach (Talk | contribs)
(New page: Often there is more than one type of ''"users"'' of an API. As 3SidesToEveryAPI explains, there is always at least the API] author point of view and [[API user point of view. B...)
Next diff →
Revision as of 13:37, 26 April 2012
Often there is more than one type of "users" of an API. As 3SidesToEveryAPI explains, there is always at least the [[API] author point of view and API user point of view. But from time to time there may be even more parties involved in design and consumption of an API. Depending on how closely related to the API specification those are, we can group them into API proximity categories.
The most distant group of users for the users of the ClientAPI - e.g. those that make calls into existing API objects, but those that don't implement them. In spite there are differences among this group as well, let's ignore them for now.
Talk about: SimpleLibrary.
Talk about: ModularLibrary with 1-N and N-M proximities.
Follow
