{"action":"closed","issue":{"url":"https://api.github.com/repos/cult-of-coders/redis-oplog/issues/51","repository_url":"https://api.github.com/repos/cult-of-coders/redis-oplog","labels_url":"https://api.github.com/repos/cult-of-coders/redis-oplog/issues/51/labels{/name}","comments_url":"https://api.github.com/repos/cult-of-coders/redis-oplog/issues/51/comments","events_url":"https://api.github.com/repos/cult-of-coders/redis-oplog/issues/51/events","html_url":"https://github.com/cult-of-coders/redis-oplog/issues/51","id":191371788,"number":51,"title":"Latency compensation doesn't work properly","user":{"login":"maxnowack","id":186073,"avatar_url":"https://avatars.githubusercontent.com/u/186073?v=3","gravatar_id":"","url":"https://api.github.com/users/maxnowack","html_url":"https://github.com/maxnowack","followers_url":"https://api.github.com/users/maxnowack/followers","following_url":"https://api.github.com/users/maxnowack/following{/other_user}","gists_url":"https://api.github.com/users/maxnowack/gists{/gist_id}","starred_url":"https://api.github.com/users/maxnowack/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/maxnowack/subscriptions","organizations_url":"https://api.github.com/users/maxnowack/orgs","repos_url":"https://api.github.com/users/maxnowack/repos","events_url":"https://api.github.com/users/maxnowack/events{/privacy}","received_events_url":"https://api.github.com/users/maxnowack/received_events","type":"User","site_admin":false},"labels":[{"id":472419170,"url":"https://api.github.com/repos/cult-of-coders/redis-oplog/labels/bug","name":"bug","color":"ee0701","default":true}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":16,"created_at":"2016-11-23T20:23:07Z","updated_at":"2016-11-25T09:40:22Z","closed_at":"2016-11-25T09:40:22Z","body":"As mentioned in [this post](https://forums.meteor.com/t/meteor-scaling-redis-oplog-status-1-0-11/30855/207?u=maxnowack), I've noticed an issue with latency compensation / optimistic ui.\r\nThe changed documents will be synced to the client, after the result of a method was received. That causes some flickering. The method on the client side will be reverted because the changes were not sent by the server before the method result was received.\r\nThe normal behavior is, that the changes were synced, while the client is waiting for the method result. After the result was received, the client compares invalidates the local working copy (minimongo) and takes the current state from the server.\r\n\r\nDDP behavior with redis oplog:\r\n![image](https://cloud.githubusercontent.com/assets/186073/20576956/667afe20-b1c0-11e6-8935-4f7ef5b62cd7.png)\r\n\r\nNormal DDP behavior:\r\n![image](https://cloud.githubusercontent.com/assets/186073/20576966/73ab3dc6-b1c0-11e6-8108-0bffa4900ef4.png)\r\n"}}
{"actor":{"display_login":"theodorDiaconu"}}