dido:public:s_cli:05_contents:01_prt:02_basics:01_commondef:api
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:s_cli:05_contents:01_prt:02_basics:01_commondef:api [2021/04/30 15:34] nick |
dido:public:s_cli:05_contents:01_prt:02_basics:01_commondef:api [2022/01/15 14:48] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== 2.1.2.1 Definition: Application Programming Interface (API) ====== | + | ====== 2.1.1 Definition: Application Programming Interface (API) ====== |
| - | [[dido:public:s_cli:05_contents:02_basics:commondef | Return to Common Definitions]] | + | [[dido:public:s_cli:05_contents:01_prt:02_basics:01_commondef:start| Return to Common Definitions]] |
| An [[dido:public:ra:xapend:xapend.a_glossary:a:api]] defines a formal set of reusable digital protocols, routines, functions and/or commands for | An [[dido:public:ra:xapend:xapend.a_glossary:a:api]] defines a formal set of reusable digital protocols, routines, functions and/or commands for | ||
| Line 11: | Line 11: | ||
| )) | )) | ||
| - | Sometimes the API is a standard developed independently of any specific component. Other times the API is developed by a "utility" component for use by may other components. Examples of standardized APIs are [[dido:public:ra:xapend:xapend.b_stds:tech:iso:dblang-sql-part1 | SQL]] and [[dido:public:ra:xapend:xapend.b_stds:tech:ieee:posix | POSIX]]. Examples of a component centric API are [[https://developers.google.com/sheets/api | Google Sheets]], the [[https://www.grapecity.com/documents-api-word | MS Word .NET API]], or the [[https://tomcat.apache.org/tomcat-9.0-doc/api/org/apache/catalina/startup/Tomcat.html | Tomcat API]]. APIs should not be confused with [[dido:public:ra:xapend:xapend.a_glossary:g:gui]]. (( | + | Sometimes the API is a standard developed independently of any specific component. Other times the API is developed by a "utility" component for use by may other components. Examples of standardized APIs are [[dido:public:ra:xapend:xapend.a_glossary:s:sql | SQL]] and [[dido:public:ra:xapend:xapend.b_stds:tech:ieee:1003.1| POSIX]]. Examples of a component centric API are [[https://developers.google.com/sheets/api | Google Sheets]], the [[https://www.grapecity.com/documents-api-word | MS Word .NET API]], or the [[https://tomcat.apache.org/tomcat-9.0-doc/api/org/apache/catalina/startup/Tomcat.html | Tomcat API]]. APIs should not be confused with [[dido:public:ra:xapend:xapend.a_glossary:g:gui]]. (( |
| GeeksForGeeks, | GeeksForGeeks, | ||
| __Difference between API and GUI__, | __Difference between API and GUI__, | ||
| Line 20: | Line 20: | ||
| <figure ApiUsage> | <figure ApiUsage> | ||
| - | {{ dido:public:s_cli:05_contents:02_basics:screen_shot_2021-04-17_at_12.22.56_pm.png?400 |}} | + | {{ dido:public:s_cli:05_contents:01_prt:02_basics:screen_shot_2021-04-17_at_12.22.56_pm.png?400 |}} |
| <caption></caption> | <caption></caption> | ||
| </figure> | </figure> | ||
| - | In Figure {{ref>ApiUsage}}, the API is comprised of methods (i.e., procedures or functions) and [[dido:public:ra:xapend:xapend.a_glossary:c:communication_protocol | protocols]]. The APIs provide an interface between components within the system, the can access utilities (i.e., [[dido:public:ra:xapend:xapend.d_opsys ||Operating System]], [[dido:public:ra:xapend:xapend.a_glossary:d:dbms]], etc.) or they can provide a service (i.e, Geographic Location, Credit Card Authorization or access to address books, etc.). Depending on the system being built, the Component, Utility or Service can be part of the same computer or distributed to other computers usually using TCP networks, but could also be [[dido:public:ra:xapend:xapend.a_glossary:b:bluetooth]], [[dido:public:ra:xapend:xapend.a_glossary:z:zigbee]], [[dido:public:ra:xapend:xapend.a_glossary:n:nfc]], etc.) | + | In Figure {{ref>ApiUsage}}, the API is comprised of methods (i.e., procedures or functions) and [[dido:public:ra:xapend:xapend.a_glossary:c:communication_protocol | protocols]]. The APIs provide an interface between components within the system, the can access utilities (i.e., [[dido:public:ra:xapend:xapend.d_opsys:start||Operating System]], [[dido:public:ra:xapend:xapend.a_glossary:d:dbms]], etc.) or they can provide a service (i.e, Geographic Location, Credit Card Authorization or access to address books, etc.). Depending on the system being built, the Component, Utility or Service can be part of the same computer or distributed to other computers usually using TCP networks, but could also be [[dido:public:ra:xapend:xapend.a_glossary:b:bluetooth]], [[dido:public:ra:xapend:xapend.a_glossary:z:zigbee]], [[dido:public:ra:xapend:xapend.a_glossary:n:nfc]], etc.) |
dido/public/s_cli/05_contents/01_prt/02_basics/01_commondef/api.1619811287.txt.gz · Last modified: 2021/04/30 15:34 by nick
