mozilla-mobile/android-components

Sync debouncing should respect SyncEngines

MatthewTighe opened this issue · 1 comments

Now that syncNow supports specifying sync engines, the debounce mechanism in the SyncManager should only debounce requests from the same engine. For example:

  • Tabs sync is initiated
  • Full sync is initiated with debounce = true

The full sync will now be debounced, even if the intention was to only debounce if a full sync had occured within the time out.

Each engine should be separately tracked so that it can be separately debounced, and full syncs should only be debounced if every supported engine has been debounced within the timer.

┆Issue is synchronized with this Jira Task