Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
In ROP, NodePropertyChangeOperation events are sent from the client to the server on commit. These make up a ObjectContextChangeLog and are applied in order on the server. However this results in excess network traffic in situations where the client application might update attributes many times before commit. In our case, we update on every keystroke.
Currently, ObjectContextChangeLog is an ArrayList of GraphDiffs (NodePropertyChangeOperations in this situation). Markers seem to also separate groups of GraphDiffs (is this for rollback and nested transactions?)
Should this become an ArrayList of markerGroups, each of is a Map<ObjectAttribute, GraphDiff> and therefore redundant events will not end up in the ObjectContextChangeLog? Or is this too simplistic...