4 ms·
Firebase (even without offline persistence) uses a simple last write wins strategy. This will work well with most apps. However, if this is not enough, our secu
by jonnydee 11y ago
Firebase (even without offline persistence) uses a simple last write wins strategy. This will work well with most apps. However, if this is not enough, our security rules allow you to have more complex strategies based on client time, for example. Even without offline it really depends on the kind of conflict resolution you want in your app. For complex apps that require merges we recommend to build something like operational transform on top of Firebase (As an example look at Firepad [1]).
[1] http://www.firepad.io/ http://www.firepad.io/
- bsaul 11y agoCould you add more detail as to what you mean by "last write" ? Is it the time at which the write was performed locally, or the time at which it was sent to the server ? the difference can be quite large if for example you connect a device after having worked offline with it for a long time.