24 Apr
2023
24 Apr
'23
3:43 p.m.
Dear all,
I am looking for some hooking mechanism for user defined routing blocks.
Is something like this already available?
1) a common part of the routing configuration shall not (or only slightly) be changed,
after some hooks have been implemented
Something like a function "engage_hooks()" of some
"hook_module"?
:
Routing config that should not be changed by application developers
engage_hooks(HOOK_TYPE);
Routing config that should not be changed by application developers
:
2) one application developer may "hook" new parts of the routing configuration
into this, by
modparam("hook_module", "hook",
"name=MY_RB;type=HOOK_TYPE;prio=50);
:
:
Route [MY_RB] {
Do something at hook HOOK_TYPE;
}
:
:
3) another application developer might want to "hook" into the same HOOK_TYPE
with a higher priority
modparam("hook_module", "hook",
"name=ANOTHER_RB;type=HOOK_TYPE;prio=20);
:
:
Route [ANOTHER_RB] {
Do another thing with higher priority at hook HOOK_TYPE
}
:
:
Kr,
Christoph