Explain hook action calling order in more detail

diff --git a/lib/ns/include/ns/hooks.h b/lib/ns/include/ns/hooks.h
index 0f6ff88c4c2fa5686f859962d71550216e4786d4..d2d310183ce88abe9a8dc6152530b272832c97f9 100644 (file)
--- a/lib/ns/include/ns/hooks.h
+++ b/lib/ns/include/ns/hooks.h
@@ -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:
  *