You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current limitation of not having the possibility to provide static listener/route hook resources leads to projects having a huge scheduler configuration where the hooks are refreshed (re-added) periodically.
It would be useful to define static hook resources, because hooks which have to be updated (or re-added) periodically are in fact static.
When using the scheduler approach, there's also a small problem where the scheduler entries are processed with a delay on server startup. This can lead to a short time right after server startup where already requests arrive, but the hooks are not yet ready.
The text was updated successfully, but these errors were encountered:
The current limitation of not having the possibility to provide static listener/route hook resources leads to projects having a huge scheduler configuration where the hooks are refreshed (re-added) periodically.
It would be useful to define static hook resources, because hooks which have to be updated (or re-added) periodically are in fact static.
When using the scheduler approach, there's also a small problem where the scheduler entries are processed with a delay on server startup. This can lead to a short time right after server startup where already requests arrive, but the hooks are not yet ready.
The text was updated successfully, but these errors were encountered: