Commit 2c34023a authored by Matthijs Mekking's avatar Matthijs Mekking 🏡 Committed by Michał Kępień

Explain hook action calling order in more detail

parent 07388903
Pipeline #9585 passed with stages
in 16 minutes and 16 seconds
......@@ -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:
*
......
Markdown is supported
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