When resolving conflict on the client listener gets notified about conflict and then sends data to the server. The listener is notified about the changes, but they are still not applied to the server.
When conflict is resolved on the server we notify client instantly.
When resolving conflict on the client it may happen that now we going to get more than one conflict for the same change (or set of the changes for the same object) which will trigger multiple notifications. Developers do not have the ability to differentiate and react to those differences.
h3. Expected behavior
We should add a flag to the listener to give developers information if conflict was resolved (server) or there will be an attempt to resolve it on a server.
We do not have also information about a successful resolution on the server after request.
When we forward request we do not listen to return (response) and ignoring that completely.
Happy for us failed requests going to be visible in UI.
Proper way will be to have `ConflictListener` have 2 methods.
(conflictOccurred and conflictResolved) and handle that properly for client side resolution
|
|
