The API Performance Contract.
The article examines application programming interfaces (API) in computer programming. The performance contract, the expectations of API performance from users of a computer system and its software, is considered. A taxonomy of API functions is offered. API behavior in response to call failures is d...
| Publicado en: | Communications of the ACM Vol. 57; no. 3; pp. 45 - 52 |
|---|---|
| Autores principales: | , |
| Formato: | Artículo |
| Publicado: |
Association for Computing Machinery
Mar2014
|
| Materias: | |
| Acceso en línea: | Ver este registro en EBSCOhost |
| fields | @attributes: recordID: 1 pdfLink: plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=94803455&site=ehost-live header: @attributes: shortDbName: hlh uiTerm: 94803455 longDbName: Humanities International Complete uiTag: AN controlInfo: bkinfo: jinfo: jid: 00010782 ACM jtl: Communications of the ACM issn: 00010782 maglogo: N pubinfo: dt: Mar2014 vid: 57 iid: 3 pid: 68 pub: Association for Computing Machinery artinfo: ui: 94803455 10.1145/2576792 ppf: 45 ppct: 7 formats: tig: atl: The API Performance Contract. aug: au: SPROULL, ROBERT F. WALDO, JIM affil: Adjunct faculty member of the computer science department, University of Massachusetts (Amherst) Professor of the practice of computer science, Harvard University su: Programming languages Computer programming Automatic programming (Computer science) Software architecture Computer software quality control Software reliability sug: subj: Programming languages Computer programming Automatic programming (Computer science) Software architecture Computer software quality control Software reliability ab: The article examines application programming interfaces (API) in computer programming. The performance contract, the expectations of API performance from users of a computer system and its software, is considered. A taxonomy of API functions is offered. API behavior in response to call failures is discussed. The dependence of major application programs on adherence to a performance contract is discussed. Means by which programmers can prevent violations of API performance contracts are examined including selection of program structure, maintaining contract stability and explicitly including the contract in API specifications. pubtype: Periodical doctype: Article src: R language: English refInfo: copyright: @attributes: flag: Y dt: @attributes: year: 2014 holdings: @attributes: islocal: N |
|---|