About offline synchronization
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.5k
- Forks
- 456
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
I needs to add a feature about offline synchronization. The scene is as follows, A and B are collaborating. A goes offline and performs some operations, and then closes the browser. I will store these ops in indexedDB. These operations will be read first after A open browser at next time. How should I deal with these ops, send them directly to the server or resolve the conflict locally first?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing ShareDB’s existing synchronization and Operational Transformation flow, then trace how operations stored in IndexedDB would be read when the browser reconnects. Compare sending queued operations directly to the server with resolving conflicts locally; done requires a decided, documented synchronization strategy and an implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100