popduke commented on issue #218:
URL: https://github.com/apache/bifromq/issues/218#issuecomment-3721632003
SettingProvider is intentionally designed to take effect eventually, driven
by its caching semantics:
1. Cache miss / value unavailable at evaluation time
If the provider does not (or cannot) supply a value when a setting is
needed, BifroMQ falls back to the setting’s initial value by default (i.e., it
does not synchronously call `provide` on cache miss unless explicitly enabled).

2. Session-scoped “sticky” behavior
Some settings that are evaluated at connection (session) establishment time
are effectively pinned for the lifetime of that connection and will not reflect
subsequent updates until the client reconnects.
For full details, please refer to the Setting Provider
[documentation](https://bifromq.apache.org/docs/plugin/setting_provider/intro/
). 
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
