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

Can this be used in a mobile app that could go offline for long periods? #16

Open
Didericis opened this issue May 22, 2018 · 5 comments

Comments

@Didericis
Copy link

I'd like to build an app that allows a user to edit encrypted journal entries. If they edit an entry on their computer while offline, edit the same entry on their phone while offline, and then both devices go online, I'd like those two entries to be reconciled.

The readme suggests this project can handle delays and race conditions/does some form of reconciliation, but it doesn't seem to be designed for long periods of users being offline. Is that correct? If it's not set up for long periods of being offline, do you have a rough idea how hard it would be to make that work?

@coderstar1234

This comment was marked as spam.

@coderstar1234

This comment was marked as spam.

@michitux
Copy link

@coderstar1234 is not affiliated with the XWiki project and definitely not a mentor. Actual contributions are of course welcome, nevertheless.

@coderstar1234
Copy link

Ok...

@mudassir-jmi
Copy link

  1. Implement a local storage mechanism on each device to store the encrypted journal entries while offline. This can be achieved using technologies like IndexedDB or local file storage.
  2. Develop a conflict detection mechanism to identify conflicts that may arise when the same entry is modified on multiple devices while offline.
  3. Design a user interface that communicates conflicts clearly and provides a seamless experience for users to resolve conflicts when devices come online.****

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

No branches or pull requests

4 participants