Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refreshable HTTP getters #727

Open
ppcad opened this issue Dec 12, 2024 · 0 comments
Open

Refreshable HTTP getters #727

ppcad opened this issue Dec 12, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@ppcad
Copy link
Collaborator

ppcad commented Dec 12, 2024

Right now HTTP getters don't get refreshed if the result at the HTTP endpoint changes.
To achieve a refresh behavior HTTP getters could periodically poll if their values have changed.
Once a change has been detected, HTTP getters could communicate this so that the new values can be used.

The refresh period could be tied to the configuration refresh interval and it might trigger a configuration reload if a HTTP getter was used in a configuration file.
Futhermore, HTTP getters could communicate changes directly by calling a callback function that has been provided to them on creation (in code).
Alternatively or additionally, a detected change could trigger a reload, even if it's not part of a configuration file, instead of using a callback. However this is expensive if a value changes often and if no full reload would be necessary.

This functionality is not always required so it should be optional.

@ppcad ppcad added the enhancement New feature or request label Dec 12, 2024
@ppcad ppcad self-assigned this Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant