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

Better to wait before dirtying again #98

Open
redgeoff opened this issue Jan 20, 2018 · 0 comments
Open

Better to wait before dirtying again #98

redgeoff opened this issue Jan 20, 2018 · 0 comments

Comments

@redgeoff
Copy link
Owner

At

return this.dirtyIfCleanOrLocked(conflictedDBNames)
(and the similar code for the change-listener) it would probably be better to say wait a random amount from 1 to 1,000 ms before dirtying again in the event that there are conflicts. This should cut down on two update-listeners attempting to dirty the same items repeatedly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant