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

Think about a proper caching strategy #13

Open
matze opened this issue Oct 31, 2013 · 0 comments
Open

Think about a proper caching strategy #13

matze opened this issue Oct 31, 2013 · 0 comments

Comments

@matze
Copy link
Contributor

matze commented Oct 31, 2013

Currently, every access to a property will lead to a query of the corresponding hardware property. This increases the perceived latency in some applications, e.g. in the control GUI due to the property tree. Moreover, in 99% of the cases the values will never change except for when the user does so.

We have to think about a general way to allow caching yet always provide the correct value. For example, any temperature property must return the correct value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant