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

Preserve oldest sensor status on purges #27

Open
jxmot opened this issue Nov 8, 2018 · 2 comments
Open

Preserve oldest sensor status on purges #27

jxmot opened this issue Nov 8, 2018 · 2 comments
Assignees
Labels
enhancement Investigating Issue is being investigated, will need to determine overall effort vs reward and all risks involved. Mid Priority

Comments

@jxmot
Copy link
Owner

jxmot commented Nov 8, 2018

The status purge erases the oldest sensor status and the client field goes blank. Improve the purge process so that it will retain the oldest status record.

@jxmot jxmot self-assigned this Nov 8, 2018
@jxmot jxmot added enhancement Investigating Issue is being investigated, will need to determine overall effort vs reward and all risks involved. labels Nov 8, 2018
@jxmot
Copy link
Owner Author

jxmot commented Mar 22, 2019

Currently, the last status message is retained only until a restart of the server. To fix that : when a new status arrives the server will save it in a text file. The next time the server starts it will read those files|that file and repopulate the internal storage of the last status. This is done before the server begins listening for clients. The same could also be done for the last sensor update(s).

The file(s) will have a depth of 1 for the status and update for each previously connected devices.

jxmot added a commit that referenced this issue Aug 27, 2020
Preserve oldest sensor status on purges #27
@jxmot
Copy link
Owner Author

jxmot commented Jan 10, 2021

This feature is under test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Investigating Issue is being investigated, will need to determine overall effort vs reward and all risks involved. Mid Priority
Projects
None yet
Development

No branches or pull requests

1 participant