Comment by arendtio

> OT involves logic on the server

Why? What my app is doing is quite simple:

1. Every time the user changes something it writes the change to a journal and

2. executes the change on a local cache (to update the UI).

3. Then it starts a background sync by fetching the latest version from the server

4. executes the change on the fresh data from the server

5. uploads the transformed data with an etag to avoid overwriting parallel changes from other clients and

6. removes the change from the journal (and updates the local cache) if everything worked just fine.

So you could argue that using the etag is some kind of logic, but I think that is not what you mean with 'involves logic on the server'.

This implementation certainly doesn't work for all use-cases (e.g. high throughput/low latency), but given that it enables even offline-scenarios, I think it isn't that bad either.