Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rate-limit duplicate updates to the same object #31

Closed
diracdeltas opened this issue Jan 12, 2017 · 0 comments
Closed

rate-limit duplicate updates to the same object #31

diracdeltas opened this issue Jan 12, 2017 · 0 comments
Assignees
Labels

Comments

@diracdeltas
Copy link
Member

@diracdeltas diracdeltas commented Jan 12, 2017

browser-laptop emits two appState changes every time a history entry is modified. for the purpose of sync, this should not require sending two network requests. either browser-laptop or sync client should rate-limit updates to the same object if the updates are approximately the same, by some definition.

@diracdeltas diracdeltas self-assigned this Jan 12, 2017
diracdeltas added a commit to brave/browser-laptop that referenced this issue Apr 25, 2017
and only trigger sync when important site fields are modified.
fix #8415
may also fix brave/sync#31

test plan:
0. automated sync tests should pass
1. enable sync and go to https://example.com
2. bookmark it. you should see a message in the console indicating a record was sent.
3. close the page and visit it again. you should not see a message in the console.
4. unbookmark it. you should see a message in the console indicating a record was sent.
diracdeltas added a commit to brave/browser-laptop that referenced this issue Apr 25, 2017
and only trigger sync when important site fields are modified.
fix #8415
may also fix brave/sync#31

test plan:
0. automated sync tests should pass
1. enable sync and go to https://example.com
2. bookmark it. you should see a message in the console indicating a record was sent.
3. close the page and visit it again. you should not see a message in the console.
4. unbookmark it. you should see a message in the console indicating a record was sent.
diracdeltas added a commit to brave/browser-laptop that referenced this issue Apr 25, 2017
and only trigger sync when important site fields are modified.
fix #8415
may also fix brave/sync#31

test plan:
0. automated sync tests should pass
1. enable sync and go to https://example.com
2. bookmark it. you should see a message in the console indicating a record was sent.
3. close the page and visit it again. you should not see a message in the console.
4. unbookmark it. you should see a message in the console indicating a record was sent.
diracdeltas added a commit to brave/browser-laptop that referenced this issue Apr 27, 2017
and only trigger sync when important site fields are modified.
fix #8415
may also fix brave/sync#31

test plan:
0. automated sync tests should pass
1. enable sync and go to https://example.com
2. bookmark it. you should see a message in the console indicating a record was sent.
3. close the page and visit it again. you should not see a message in the console.
4. unbookmark it. you should see a message in the console indicating a record was sent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

1 participant
You can’t perform that action at this time.