Support latency compensation #4
Description
Currently if one for example publishes a count of documents from the server side using subscription data, when there is a method which simulates a change on the client side, the count is not updated until the server confirms the change. That might be or not be want a developer wants. It would be great if there could be an option to also do latency compensation for subscription data. I do not know how though. Probably we should define a simulated code for the client side for this purpose. So every subscription data field should have a client-side simulation function as well? Or for whole data one simulation function?