---
* providing information about what hooks have been registered for events
and related statistical data.
...
A hook is limited to specifying only *1* hint for itself. If either the
"before" or "after" hints are used, the hook specified by the name supplied
with the hint *must* already exist on the hook chain associated with the
event.
---
If there is not a mechanism for a module to find out what hooks
have been registered, how does a module use the before or after
hints? Is it assumed that somehow the module will know the
names of other hooks in the chain?
---
Example 1.
If hook A is registered for event E first, and asks to be placed first
on the list, then this will be done. If a later hook, B, is registered
for event E, it may either ask to be placed before A or to be placed in
the first position. In satisfing either of these requests, the initial
hint is no longer true - hook A is now second.
---
Can there be a mechanism to notify the owner of hook A
that its position is now changed after hook B is registered?
Then the owner of hook A can decide if this is OK. If not OK,
it may notify the user that A may not work properly now and
some actions are needed.
--
K. Poon.
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
