| Revision as of 23:20, 29 October 2010 editAbhayakara (talk | contribs)Extended confirmed users761 edits Propose the article for deletion← Previous edit | Revision as of 22:07, 12 July 2012 edit undoPratyeka (talk | contribs)Extended confirmed users8,789 edits clear delete boxNext edit → | ||
| Line 1: | Line 1: | ||
| {{Proposed deletion/dated | |||
| |concern = this is a very obscure protocol, and I don't think it's notable | |||
| |timestamp = 20101029232007 | |||
| }} | |||
| {{Orphan|date=November 2006}} | {{Orphan|date=November 2006}} | ||
| '''OMAPI''' is an ] that stands for '''Object Management Application Programming Interface'''. It is currently used by ] as an ] to manipulate the internal ] of a running ] in a ] way; the allowed modifications cannot impact the functioning server. | '''OMAPI''' is an ] that stands for '''Object Management Application Programming Interface'''. It is currently used by ] as an ] to manipulate the internal ] of a running ] in a ] way; the allowed modifications cannot impact the functioning server. | ||
Revision as of 22:07, 12 July 2012
 | This article is an orphan, as no other articles link to it. Please introduce links to this page from related articles; try the Find link tool for suggestions. (November 2006) |
OMAPI is an acronym that stands for Object Management Application Programming Interface. It is currently used by ISC DHCP as an API to manipulate the internal data structure of a running server in a secure way; the allowed modifications cannot impact the functioning server.
Operations
- Shutting down or reloading the server
- Partially modifying internal data structure such as leases or host
- Modifying status of objects such as failover relationship
Offering a well-defined API to access the data is an example of «barricade» in software engineering.
References
- Code complete 2nd Edition Steve McConnell: Defensive Programming
- DHCP: OMAPI