This is an old revision of this page, as edited by GregJackP (talk | contribs) at 15:13, 25 January 2013 (Nominated for deletion; see Misplaced Pages:Articles for deletion/OMAPI. (TW)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 15:13, 25 January 2013 by GregJackP (talk | contribs) (Nominated for deletion; see Misplaced Pages:Articles for deletion/OMAPI. (TW))(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)| An editor has nominated this article for deletion. You are welcome to participate in the deletion discussion, which will decide whether or not to retain it.Feel free to improve the article, but do not remove this notice before the discussion is closed. For more information, see the guide to deletion. Find sources: "OMAPI" – news · newspapers · books · scholar · JSTOR%5B%5BWikipedia%3AArticles+for+deletion%2FOMAPI%5D%5DAFD |
 | This article may be too technical for most readers to understand. Please help improve it to make it understandable to non-experts, without removing the technical details. (July 2012) (Learn how and when to remove this message) |
 | 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 instance of the ISC DHCP server or client. Uses on the server include editing registration information for managed nodes and controlling the operation of the DHCP Failover Protocol. Uses on the client include fetching configuration information, releasing and renewing leases, and changing which interfaces are managed by the DHCP client.
References
- DHCP: OMAPI