Handling Server-Deletions in Store5 Sync: Strategies & Best Practices

[blakelee]

I’m working on keeping my server in sync with the client. One challenge I’m facing is handling deleted data on the server. Since the server doesn’t return deleted items, Store5 doesn’t automatically detect them, which leaves stale records on the client.

Here are the approaches I’m considering:

• The Bookkeeper already tracks syncs, which might be useful in detecting missing items. If an item is in the Bookkeeper and has been synced but is out of synced, eventually there can be a validity check that invalidates it. If it has never been synced then the server knows to insert a new item.
• Another idea is to send all client-side IDs to the server, keeping a graveyard of deleted IDs on the server to compare against.

However, I’m unsure of the best way to approach this and whether Store5 has a built-in or recommended strategy for handling deletions.

Questions:

1. How have others handled deletions in a Store-based sync system?
2. Are there any best practices, articles, or examples on dealing with server-side deletions in a sync mechanism?
3. Would Store5 benefit from a built-in deletion detection mechanism?

Would love to hear thoughts, experiences, or alternative approaches! Conflict resolution strategies in sync systems are tricky, and I want to avoid reinventing the wheel.

Thanks in advance!

[matt-ramotar]

RFC: #697