mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-31 14:35:26 +00:00
Code Issues Releases Wiki Activity

Merge branch 'michal/explain-hook-action-calling-order-in-more-detail' into 'master'

Browse Source 
Explain hook action calling order in more detail

See merge request isc-projects/bind9!1451
This commit is contained in:
Matthijs Mekking
2019-02-06 05:08:25 -05:00
parent 0738890313 2c34023a5e
commit 9bc600eff2
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
lib/ns/include/ns/hooks.h
View File

@@ -85,8 +85,14 @@
* In order for a hook action to be called for a given hook, a pointer to that
* action function (along with an optional pointer to action-specific data) has
* to be inserted into the relevant hook table entry for that hook using an
* ns_hook_add() call. If multiple actions are set up at a single hook point,
* they are processed in FIFO order.
* ns_hook_add() call. If multiple actions are set up at a single hook point
* (e.g. by multiple plugin modules), they are processed in FIFO order, that is
* they are performed in the same order in which their relevant ns_hook_add()
* calls were issued. Since the configuration is loaded from a single thread,
* this means that multiple actions at a single hook point are determined by
* the order in which the relevant plugin modules were declared in the
* configuration file(s). The hook API currently does not support changing
* this order.
*
* As an example, consider the following hypothetical function in query.c:
*