Implement caching in case of WebDAV synchronisation #3

New Issue

2025-07-01T10:08:26+02:00

chepycou commented

2025-07-01 10:08:26 +02:00

Rationale

The user should be able to read past logs and input some log even without internet connection / when the WebDAV server is down.

Proposed change

The app should keep the last synchronized JSON file on device as a cache,
This JSON should be displayed/edited in place of the remote JSON when waiting for the server to be reached (if for instance a timeout of .5 or 1 second is reached).
When the remote JSON is fetched, both should be merged (for instance by taking the concatenation of both JSONs and removing duplicate timestamps, but there should be a better way of merging)

Small improvements along the way

Add a small "not yet uploaded" icon next to the not yet synchronized logs
And/or add a header at the top warning that all changes have not yet been synchronized. This way, one parent can be reminded to turn off airplane mode, so the other gets the data too, for instance.

## Rationale The user should be able to read past logs and input some log even without internet connection / when the WebDAV server is down. ## Proposed change - The app should keep the last synchronized JSON file on device as a cache, - This JSON should be displayed/edited in place of the remote JSON when waiting for the server to be reached (if for instance a timeout of .5 or 1 second is reached). - When the remote JSON is fetched, both should be merged (for instance by taking the concatenation of both JSONs and removing duplicate timestamps, but there should be a better way of merging) ## Small improvements along the way - Add a small "not yet uploaded" icon next to the not yet synchronized logs - And/or add a header at the top warning that all changes have not yet been synchronized. This way, one parent can be reminded to turn off airplane mode, so the other gets the data too, for instance.

penguin86 commented

2025-07-02 18:38:48 +02:00

Merging is always tricky to implement correctly. But yes, when I decided the format, I thought the timestamp to be the unique identifier and the way to merge two datasets (because it also defines ordering).

👍 1

Ghost commented

2025-09-16 10:15:48 +02:00

Maybe also have a synchronize icon that is cut or greyed out, or a yellow triangle with an exclamation mark as identifier symbols to the records that are not yet synced.

Regardless, if something happens with the webdav server, currenlty there is no way to add records, unless we disable webdav. Not sure what happens with the data if we switch to local and then to remote again.

Maybe also have a synchronize icon that is cut or greyed out, or a yellow triangle with an exclamation mark as identifier symbols to the records that are not yet synced. Regardless, if something happens with the webdav server, currenlty there is no way to add records, unless we disable webdav. Not sure what happens with the data if we switch to local and then to remote again.

👍 1

Sign in to join this conversation.

3 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: penguin86/luna-tracker#3