|
|
|
|
|
|
by ris58h
1328 days ago
|
|
|
> If I understand things correctly this is the missing piece: persistence. So if the user goes offline and makes changes, those will persist so they can be synced when the user goes online again. 1. You can persist data with localStorage/IndexDB, can't you?
2. There is nothing in the article about syncing. There is no out-of-the-box solution, as I can see. |
|
|
I guess so, but given the situation that I'd already be using WASM SQLite in the client's browser, then I'd have to implement that part myself, or use something like Absurd SQL. I'd rather use the implementation made by the creator of SQLite.
> There is nothing in the article about syncing.
Correct, that's something I'll have to do myself. I don't see any issues there though, I'd just need to verify the user is authorised to make those changes, which in my specific use case seems pretty trivial.