OMAPI: Difference between revisions

Browse history interactively ← Previous edit Next edit →Content deleted Content addedVisual WikitextInline

Revision as of 13:23, 18 July 2012 editAbhayakara (talk \| contribs)Extended confirmed users761 edits Oops, forgot to make "nodes" wiki link link to the right page.← Previous edit		Revision as of 11:45, 31 July 2012 edit undoJmajeremy (talk \| contribs)Extended confirmed users, File movers, Rollbackers3,120 edits Added {{technical}} tag to article (TW)Next edit →
Line 1:		Line 1:
			{{technical\|date=July 2012}}
	{{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 instance of the ISC DHCP ] or ]. Uses on the server include editing registration information for managed ] and controlling the operation of the ]. Uses on the client include fetching configuration information, releasing and renewing leases, and changing which interfaces are managed by the DHCP client.		'''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 instance of the ISC DHCP ] or ]. Uses on the server include editing registration information for managed ] and controlling the operation of the ]. Uses on the client include fetching configuration information, releasing and renewing leases, and changing which interfaces are managed by the DHCP client.

Revision as of 11:45, 31 July 2012

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

Categories:

Revision as of 13:23, 18 July 2012 editAbhayakara (talk \| contribs)Extended confirmed users761 edits Oops, forgot to make "nodes" wiki link link to the right page.← Previous edit		Revision as of 11:45, 31 July 2012 edit undoJmajeremy (talk \| contribs)Extended confirmed users, File movers, Rollbackers3,120 edits Added {{technical}} tag to article (TW)Next edit →
Line 1:		Line 1:
			{{technical\|date=July 2012}}
	{{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 instance of the ISC DHCP ] or ]. Uses on the server include editing registration information for managed ] and controlling the operation of the ]. Uses on the client include fetching configuration information, releasing and renewing leases, and changing which interfaces are managed by the DHCP client.		'''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 instance of the ISC DHCP ] or ]. Uses on the server include editing registration information for managed ] and controlling the operation of the ]. Uses on the client include fetching configuration information, releasing and renewing leases, and changing which interfaces are managed by the DHCP client.