Marak / Marak/node-backbone-request
sync architecture
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 9
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
nice stuff
I wonder how you handle the issues of sync merge problems ?
Also on the server you need a NOSQL type setup to get around foreign Key constraints
And to know what the client needs to be updated with you need some sort of persistent channel ?
G
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
The issue names no files, tests, or entry points. Start by reading the repository's existing synchronization code and determine how merge conflicts, server persistence, and client update notification are currently handled. The work is not ready to begin until those requirements and an implementation boundary are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100