The rate-limiter can load the limits configuration from the backend service, where it might be generated dynamically. It could be useful to trigger some custom action (some logging, sending an event to https://github.com/prezi/changelog, ...) whenever the rate-limiter loads a new limits configuration that was actually different from the one it was working with before.
The rate-limiter can load the limits configuration from the backend service, where it might be generated dynamically. It could be useful to trigger some custom action (some logging, sending an event to https://github.com/prezi/changelog, ...) whenever the rate-limiter loads a new limits configuration that was actually different from the one it was working with before.