Commit 7fef2d7f authored by Tomek Mrugalski's avatar Tomek Mrugalski 🛰
Browse files

[3063] Minor corrections in Maintenance Guide.

parent 1463b501
......@@ -31,7 +31,7 @@
@section hooksmgObjects Hooks Framework Objects
The relationships betweeh the various objects in the hooks framework
The relationships between the various objects in the hooks framework
is shown below:
@image html HooksUml.png "High-Level Class Diagram of the Hooks Framework"
......@@ -116,9 +116,13 @@
a copy of the vector is taken before the iteration starts. The @ref
hooksmgCalloutManager iterates over this copy while any changes made
by the callout registration functions affect the relevant callout vector.
Such approach was chosen because of performance considerations.
@subsection hooksmgServerObjects Server-Side Objects
Those objects are not accessible by user libraries. Please do not
attempt to use them if you are developing user callouts.
@subsubsection hooksmgServerHooks Server Hooks
The singleton @ref isc::hooks::ServerHooks object is used to register
......@@ -195,7 +199,7 @@
The @ref isc::hooks::CalloutManager is the core of the framework insofar
as the registration and calling of callouts is concerned.
It maintains a "hook vector - a vector with one element for
It maintains a "hook vector" - a vector with one element for
each registered hook. Each element in this vector is itself a
vector (the callout vector), each element of which is a pair of
(library index, callback pointer). When a callout is registered, the
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