1899433 - Create a backoff strategy for unsuccessful closing of remote tabs

Status: NEW

(Firefox :: Sync, task, P3)

Description

[Sammy Khamis [:skhamis]]

After https://phabricator.services.mozilla.com/D208419 lands. We'll still need to devise a proper back-off strategy for scenarios when the push fails to send. Right now we'll just try again in 60s but we should probably do something a little more involved.

Comment 1

[Mark Hammond (PTO; back Oct-3) [:markh] [:mhammond]]

In particular, I think we want a simple exponential backoff strategy - something like try again in 5 seconds, every failure double that until a max of (I don't know - 120 seconds? 5 minutes? More?), but without persisting the value (ie, browser restarts resets the timer).

Just to complicate things, we should talk to FxA to better understand their throttling strategy - let's say the user just attempted to send 1k tabs to themselves and got rate limited by FxA - it would be a very bad outcome if we tried the strategy I listed above, but all that did was extend the rate limiting imposed to FxA such that the feature never again worked for those users. In practice I think this means we might need to examine the fxa response to look for the rate limit headers and ensure we comply.

Finally, there's no good reason for desktop and mobile to differ in their approach here, so NI Lina to both (a) tell us what mobile does/plans and (b) get her opinion on the above