Commit d141c47a authored by Stephen Morris's avatar Stephen Morris
Browse files

[2342] Add programmer documentation

Also add missing library into the makefile - this showed its
absence on OS/X.
parent 3dc78f0e
......@@ -29,6 +29,7 @@
* - @subpage libdhcp
* - @subpage libdhcpIntro
* - @subpage libdhcpIfaceMgr
* - @subpage dhcp-database-backends
* - @subpage perfdhcpInternals
* @section misc Miscellaneous topics
......@@ -52,14 +52,15 @@ libb10_dhcpsrv_la_SOURCES += triplet.h
libb10_dhcpsrv_la_CXXFLAGS = $(AM_CXXFLAGS)
libb10_dhcpsrv_la_LIBADD = $(top_builddir)/src/lib/asiolink/
libb10_dhcpsrv_la_LIBADD = $(top_builddir)/src/lib/dhcp/
libb10_dhcpsrv_la_LIBADD += $(top_builddir)/src/lib/asiolink/
libb10_dhcpsrv_la_LIBADD += $(top_builddir)/src/lib/util/
libb10_dhcpsrv_la_LDFLAGS = -no-undefined -version-info 2:0:0
libb10_dhcpsrv_la_LDFLAGS += $(MYSQL_LIBS)
EXTRA_DIST = README database_backends.dox
# Disable unused parameter warning caused by some of the
@page dhcp-database-backends DHCP Database Back-Ends
All DHCP lease data is stored in some form of database, the interface
to this being through the Lease Manager.
All backend classes such as isc::dhcp::MySqlLeaseMgr are derived from
the abstract isc::dhcp::LeaseMgr class. This provides methods to
create, retrieve, modify and delete leases in the database.
@section dhcpdb-instantiation Instantiation of Lease Managers
A lease manager is instantiated through a the LeaseMgrFactory class. This
has three methods:
- isc::dhcp::LeaseMgrFactory::create - Creates a singleton Lease
Manager of the appropriate type.
- isc::dhcp::LeaseMgrFactory::instance - Returns a reference to the
the instance of the Lease Manager.
- isc::dhcp::LeaseMgrFactory::destroy - Destroys the singleton lease manager.
The selection of the Lease Manager (and thus the backend database) is
is controlled by the argument passed to isc::dhcp::LeaseMgrfactory::create.
This is a string containing a set of "keyword=value" pairs (no embedded
spaces), each pair separated by a space from the others, e.g.
type=mysql user=keatest password=keatest name=keatest host=localhost
The following keywords are used for all backends:
- type - specifies the type of database backend. The following types are
- mysql - Use MySQL as the database
The following keywords apply to the MySQL backend:
- host - host on which the selected database is running. If not supplied,
"localhost" is assumed.
- name - name of the MySQL database to access. There is no default - this
must be supplied.
- password - password for the selected user ID (see below). If not specified,
no password is used.
- user - database user ID under which the database is accessed. If not
specified, no user ID is used - the database is assumed to be open.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment