Open Bug 968592 Opened 7 years ago Updated 2 years ago

Use expired tokens for info/collections fetches

Categories

(Firefox for Android :: Android Sync, defect, P5)

Firefox 29
All
Android
defect

Tracking

()

Tracking Status
fennec + ---

People

(Reporter: rnewman, Assigned: nalexander)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [qa?])

Client implementation for Bug 960878 -- we can avoid the overhead of a new token fetch if we have no local data to upload for the syncing engines, or are doing a download-only sync, and just want to check if there's anything new on the server.

This will go a long way toward making short-circuit syncs cheaper, at the cost of increasing client complexity.
Whiteboard: [qa?]
This won't make 29.
tracking-fennec: 29+ → 30+
Priority: -- → P3
Assignee: nobody → nalexander
Some work in progress commits that test that the Sync endpoints are doing the right thing are at:

https://github.com/mozilla-services/android-sync/tree/nalexander/bug-968592-expired-tokens/

Of course, the endpoints don't accept expired tokens yet, so this fails.  But the tests are useful, and the old data might be useful too.
See also Bug 985007, which should allow to set the token duration in test code.
See Also: → 985007
tracking-fennec: 30+ → +
Product: Android Background Services → Firefox for Android
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.